The ros-comm recipes are updated to 1.9.48 to be in line with
https://github.com/ros/rosdistro/blob/4551e7c32d1b34984410b79bc0ec36afe3d3d245/hydro/release.yaml.
The previously applied patches have been included in 1.9.48 and are
removed from the recipe and this repository.

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

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.

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

The rostest package requires that the rostest executable can be
found by cmake's find during configure. Hence, rostest depends on
rostest-native.
To implement this, rostest and rostest-native are defined with
different dependencies.

This commit resolves issue #83.

| CMake Warning at /build/v2012.12/build/tmp-angstrom_v2012_12-eglibc/sysroots/x86_64-linux/usr/share/catkin/cmake/test/nosetests.cmake:90 (message):
|   nosetests not found, Python tests can not be run (try installing package
|   'python-nose')

Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>

The rostopic tool needs the rosbag python module for its execution.

When importing the rosbag python module, it requires these python modules.

The topic-tools fails during the do_compile step at:
.../sysroots/x86_64-linux/usr/lib/libboost_thread-mt.so: could not read symbols: File in wrong format

The failure comes from the rostest-native package which delivers a
header file with boost dependencies and therefore add the relevant
library to the link path. Add rostest to the DEPENDS to use the
header and libraries from the cross sysroot and keep the native
rostest for the binary.

Fixed #51

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

For starting roscore, it requires a number of runtime dependencies.
At the moment, all runtime dependencies, even recursive runtime dependencies,
are added only in the roslaunch recipe. Hence, the recipe contains all
runtime dependencies.
At a later stage, one should move the recursive runtime dependencies into
the appropriate recipes.

Since its initial contribution in f73e30ae,
the topic-tools had an untested md5 hash for the license check.

The recipe contains a hyphen in their name, hence we must use the ROS_BPN
variable.

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

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

Rostest depends on its own package and therefore needs to search
in the devel space for the rostestConfig.cmake during native
build.

| CMake Error at /.../usr/share/catkin/cmake/find_program_required.cmake:5 (message):
|   rostest not found
|

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

All ROS packages with install tools in the bin directory or install
python code with is used by other packages should be used as native
version. Adapte the DEPENDS accordingly.

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>

Add the package to the dependency because the do_configure fails
as it tries to find the package.

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>