A previously written recipe for the poco library and
a special OpenEmbedded config file for poco is included from
https://gitorious.digitalstrom.org/dss-oe/dss-oe/blobs/raw/master/dS/meta-dss11-production/recipes-support/poco/poco_1.3.6p2.bb
and https://gitorious.digitalstrom.org/dss-oe/dss-oe/blobs/raw/master/dS/meta-dss11-production/recipes-support/poco/files/OE



This recipe and the config is redistributed here under the same
license agreement as the original.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>

Updating to hydro release version

When updating from 1.9.41 to 1.9.47, the commit
https://github.com/ros/ros_comm/commit/c5dfa6305e883f76dc2aa52d27d2977e3d66ea2e
adds a routine in the CMakeLists.txt to find the pthread library.
This routine is not suitable for the use with our tool chain, i.e.,
it reports an error (cf. #125) when using roscpp-native.

This commit adds a patch that reverts that change in roscpp's
CMakeLists.txt.

The previously applied patch is incorporated in the hydro release
version of the tf package. Also, the new tf package has further
dependencies.

For the update of the tf package to the hydro release version,
new recipes for the geometry-experimental repository are provided
in this commit.

The previously applied patch is now incorporated in the hydro
release version.

In this commit, the angles directory is renamed to match repository
name in hydro/release.yaml, and a patch is required probably
because of the new catkin version.

The previous patch applied specifically in the recipe is
incorporated in the new version, and was removed from the recipe.

As the license text of the xmlrpcpp changed, the license checksum
is adjusted.

The rosunit patch required some minor adjustments.

To update to the hydro release version, the genpy patch required
some minor adjustments.

To update the hydro release version, the genlisp required some
minor adjustments.

To update to the hydro release version, the gencpp patch required
some minor adjustments.

To update to the hydro release version, the genmsg patch required
some minor adjustments.

python-nose: replacing duplicate recipe that is in meta-oe by a bbappend file to have a native recipe (resolves #66)

preparations for PCL and pcl-ros package

To compile nodelet-topic-tools, we must provide a working
dynamic-reconfigure in the native sysroot. This requires
some adjustments to the native versions of the required
python modules.

In particular, the following tasks ran successfully for this
commit:

This command tests compiling rospack-native:
rm bitbake.lock cache/ sstate-cache/ tmp-eglibc/ -rf && bitbake rospack-native

This command tests compiling roslib-native:
rm bitbake.lock cache/ sstate-cache/ tmp-eglibc/ -rf && bitbake roslib-native

As nodelet-topic-tools uses rospack-native and roslib-native to
some extent (dependency: rospack-native -> roslib-native ->
dynamic-reconfigure-native -> nodelet-topic-tools), this command
tests running rospack-native and roslib-native:
rm bitbake.lock cache/ sstate-cache/ tmp-eglibc/ -rf && bitbake nodelet-topic-tools

This command tests compiling rospack and roslib:
rm bitbake.lock cache/ sstate-cache/ tmp-eglibc/ -rf && bitbake rospack
rm bitbake.lock cache/ sstate-cache/ tmp-eglibc/ -rf && bitbake roslib

All these command run with this commit without errors, and
future commits to these files should keep them run without
errors or justify modifications with better tests.

A minor open issue related to rospack is issue #116
(cf. https://github.com/bmwcarit/meta-ros/issues/116).

This commit incorporates feedback from Stefan Herbrechtsmeier.

yaml-cpp: incorporated recipe from Kartik Mohta's repository

This commit adds the yaml-cpp recipe from the repository at
https://github.com/kartikmohta/meta-km. The file is licensed
with the MIT license
(cf. https://github.com/kartikmohta/meta-km/blob/master/LICENSE).

The original recipe can be found at
https://github.com/kartikmohta/meta-km/blob/master/recipes-devtools/yaml-cpp/yaml-cpp_0.3.0.bb

The README file acknowledges Kartik Mohta's contribution and names
him as a contributor.

The bitbake call before each build of a recipe was not required.
Commented out the fresh build, as it currently does not show more
problems than simply building in a shared environment.
Avoiding a fresh environment for each build decreases the runtime
of the test dramatically.

Another patch for optionally configuring tests