Generalize construction of ros_prefix and use it consistently

festival: correcting audsp path (resolves #309)

roslaunch: Use as documented environment

ROS and catkin packages install their assets to paths prefixed by
ros_prefix. As the recipe was trying to collect the assets for the dev
package in the wrong locations, the dev package was empty.

To address this we use the ros_prefix consistently across the recipe.

In special situations, the prefix used by yocto is prefixed by an
additional staging dir and thus not always starting at /. The current
class already covered the special case for building native packages, but
was erroneous when trying to build nativesdk packages.

Instead of dealing with these special cases ourselves, we can prefix the
ros_prefix with yocto's base_prefix. This prefix will contain any
additional dirs yocto decides to use and will therefore always result in
valid directory variables automatically.

Fixing various QA warnings

Solves following warning:
QA Issue: speech-tools requires /usr/bin/perl,
but no providers in its RDEPENDS [file-rdeps]

Solves following warning:
QA Issue: roslint requires /bin/bash,
but no providers in its RDEPENDS [file-rdeps]

roscore-default: Removing not supported variable in variable
roscore-default: Adding PATH, LD_LIBRARY_PATH and PYTHONPATH
roscore.service: Using /opt/ros/hydro/bin instead of /usr/bin to launch
roscore

You can now install roslaunch-systemd :

opkg install roslaunch-systemd

and start roscore :

systemctl start roscore

Since version 1.7.15, the bondcpp package needs the cmake_modules
package. The dependency was added with this commit:
https://github.com/ros/bond_core/commit/f4265d6b28f250d95364197f2694653db9618245

This issue was reported by Gauthier Monserand (simkim -at- simkim.net).

Two new packages: razor-imu-9dof and xv-11-laser-driver

Updates until mid of November 2014

The patches in the meta-ros repository have been submitted and
included in 0.7.3 and hence are deleted in this commit.

The patch in the meta-ros repository has been submitted and
included in version 0.7.3 and hence is deleted in this commit.

After updating to 0.3.2, the patch is obsolete, and hence removed.

README: adding BBLAYERS example under USAGE

libfreenect improvements

Solves following warning:
QA Issue: libfreenect requires /bin/bash,
but no providers in its RDEPENDS [file-rdeps]

Backporting following libfreenect patch:
https://github.com/OpenKinect/libfreenect/commit/
0cbb86ec982d3e79ad5efa9d1b2b16724ae89bc5

Without this patch, libfreenect would override all compiler flags,
including any machine specific compile flags
(e.g. -mfloat-abi=hard to compile with hard floating point).

We are backporting this patch rather than upgrading to v0.4.1
where this is fixed, as v0.4.0 introduced changes that break
compatibility with the current freenect version (0.3.2).
See https://github.com/OpenKinect/libfreenect/releases/tag/v0.4.0
for the breaking changes.
See https://github.com/ros-drivers/freenect_stack/issues/12
for additional discussion.

This commit provides the autotools-brokensep class and uses it for
the wxwidgets recipe.
The autotools-brokensep indicates that this package currently cannot
handle out-of-source builds, and hence the in-source build must be
kept until this is resolved.
The autotools-brokensep class is a copy of the autotools-brokensep
class provided in the openembedded-core commit 006b8a78 [1].
To make this commit backwards compatible to even earlier versions
of openembedded-core, we provide this class in meta-ros ourselves.

[1] http://cgit.openembedded.org/openembedded-core/commit/?id=006b8a7808a58713af16c326dc37d07765334b12

minor updates till early October 2014

This commit also adds cmake-modules to the dependencies of
clear-costmap-recovery, while looking into an build issue of the
intermediate version 1.11.12(!) of navigation.