This commit intends to add the static library to the main package.
It resolves issue #82 and is a copy of a part of the catkin class.

This closes #69 and #80 with the following error:
*** No rule to make target `/usr/lib/genpy/genmsg_py.py', needed by
`devel/lib/python2.7/site-packages/std_msgs/msg/_Bool.py'.  Stop.

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

Currently, it is not clear if the additional files are required in
the normal package or the dev package. Hence, we do not touch them
(they are not added to any package or deleted after the installation)
until the right operation is clear.

Until then, the console-bridge emits the warning
WARNING: QA Issue: console-bridge: Files/directories were installed but not shipped
  /usr/share
  /usr/share/console_bridge
  /usr/share/console_bridge/package.xml
  /usr/share/console_bridge/cmake
  /usr/share/console_bridge/cmake/console_bridge-config.cmake

The class-loader 0.2.0 depends on console-bridge via cmake and not
via catkin as in version 0.1.28. This resolves issue #79.

The nodelet package.xml also lists the dependency on uuid, but the
recipe seems to work without.
It uses the SRC_URI from its ros repository (instead of the ros-gbp
repository), because in the commit
30306b6b, we agreed to use the ros
location instead of the ros-gbp location uniformly.

The pluginlib is used by the nodelet package.

The class-loader is used by the pluginlib.

The console-bridge is a cmake installation, but not a catkin package.
In its current state, the recipe compiles and installs, but the
class_loader package fails and complains with

|   catkin_package() CATKIN_DEPENDS on 'console_bridge', which has been found
|   in
|   '(...)/build/tmp-eglibc/sysroots/qemux86-64/usr/share/console_bridge/cmake/console_bridge-config.cmake',
|   but it is not a catkin package

This commit provides the current state for further discussion and
joint investigation.

This commit adds the recipes for packages bond, bondcpp, smclib
and bondpy. The first three packages are required for the nodelet
package.

| 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>

This commit uses ROS_BP in the recipes after ROS_BP was set right in
the commit 0d07506b.

The last patched version assumes that the variable msg include dirs
is only one directory and not a list of directories. This leads to
errors if generate_message(DIRECTORY ...) occurs twice in the
CMakeLists files.

Make Error at build/devel/share/cmake/...-msg-paths.cmake:2 (if):
| if given arguments:
|
| "NOT" "IS_ABSOLUTE" "" ""

Fixed issue #72.

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

The python binary path for genmsg_py.py and gensrv_py.py are hard
coded in the CMake file and don't work during cross compile. Setup
them via find_program during runtime.

This fix #69 and the following error:
*** No rule to make target `/usr/lib/genpy/genmsg_py.py', needed by
`devel/lib/python2.7/site-packages/std_msgs/msg/_Bool.py'.  Stop.

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

The rosbash tools does not run with the BusyBox shell, and requires
the bash and the common find utility.

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

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

When importing the rosbag module in python, it fails in a genpy python module
complaining about missing the shutil python module. The shutils module is
provided by python-shell.

After changing the CMakeLists files of the sources and adding the
dependencies, the three chatter recipes cross-compile.

The recipes are supposed to cross-compile and install the chatter
example. In this commit, the recipe do not contain any dependencies
and configure does not run through yet.

The recipe python-pprint rdepends on python-io. As this was not reflected in
the oe-core repository, we added the dependency in genmsg.
Now after the commit abe7bf9992e298f1b53e790eee7b064a9e4e8589 in oe-core,
we can remove the runtime dependency in genmsg.

This commit resolves issue #54.

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

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.

The roscpp-core package is a meta-package. This meta-package and the concept
meta-package in general is not used for any purpose in our layer.

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>