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

In commit 53796fc4, bitbake fails at parsing. It slipped through,
as I did not invoke any testing before submitting 53796fc4. This
commit resolves the obvious shortcoming.

The description is not indented after line breaks. All other
information, i.e., the dependencies and SRCURI, are indented with
four spaces after line breaks. Shell scripts are indented with
multiples of four spaces.

In recipes-ros, I located and checked for tabulators and spacing
with these bash commands:

egrep '^ [^ ]+' . --exclude *.patch -R
egrep '^  [^ ]+' . --exclude *.patch -R
egrep '^   [^ ]+' . --exclude *.patch -R
egrep '^    [ ]+[^ ]+' . --exclude *.patch -R

While going through the recipes and manually improving the layout,
I also adjusted the descriptions to use maximal 100 characters
per line.

After running oe-stylize.py on all recipes in recipes-ros, this
commit improves the formatting of some recipes.

To achieve this, I executed these commands in recipes-ros:
find . -name *.bb | sed 's#\(.*\)#./oe-stylize.py \1 > \1_sanitized#' | sh
find . -name *.bb | sed 's#\(.*\)#diff -Naur \1 \1_sanitized#' | sh > diffs

Then, I manually inspected the diffs file, and improved the
recipes.

For the DESCRIPTION line in the addressed recipes, the line width
of 100 characters was chosen, as the LIC_FILES_CHKSUM line and
SRC_URI line usually are also around about 100 characters long.
Hence, choosing a shorter line width, e.g. 80 characters, would
have only created more line breaks, but not reduced the need to
use a file viewer with which 100 characters line width can be
displayed. For the github file and diff viewer and most editors
on reasonably-sized screens, 100 character line width is no
problem.

In the commit 21f7799e, I manually
modified the patch, but it slipped my eyes to adjust the line
information in the patch accordingly.
This commit corrects the line information, so that the patch can
now be applied correctly.

This commit further adds a simple fix to the patch for the ros-comm
repository.

Besides updating ros-comm, this commit removes the second hash
values, that probably slipped-in during the last update.

Resolves:
  File "/usr/lib/python2.7/site-packages/rosservice/__init__.py", line 61, in <module>
    import rosmsg
ImportError: No module named rosmsg

The ros-comm 1.9.53 now also contains the new package rosbag-storage.

The ros-comm recipes are updated to 1.9.50 to be in line with
https://github.com/ros/rosdistro/blob/ef3a7449d7f7ef6e691a5724ef6c485e75cfd4af/hydro/release.yaml.

After the native packages are removed, the roscpp patch, which was
originally required for dynamic-reconfigure-native, is not needed
anymore.

When CATKIN_ENABLE_TESTING is deactivated, the ROS packages do not
require the rostest package.
This commit includes a number of patches to be submitted in the
upstream repositories and removes the rostest dependencies from
the recipes.

The native packages are not required anymore, because the needed
python scripts during compile time are also provided by the
cross-compiled packages and the python scripts are platform
independent. Only the catkin package is provided as native package.

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>