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>

genpy: Setup python binary path during runtime via find_program 

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.

This commit moves the description of previous uses in a separate file,
adds the typical information for a README of an OpenEmbedded layer and
describes the usage for the roscore image recipe.

Instead of maintaining a copy of the tinyxml recipe from the meta-oe layer, we
require that the installation also includes the meta-oe layer.
We updated the README accordingly and also updated the description of the
current setup. We also updated and tuned the CONTENT file.

This commit resolves issue #45.

some minor improvements towards running roscore

The rosversion command requires that the package.xml are available at
run time. The rosversion command is used when starting roscore.

adding some runtime dependencies

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>

This commit provides a recipe for a core image to start roscore, and
also tunes the README.

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.

In the topic-tools recipe, a QA error was raised as the .debug files were put
into the main package. By adding this line in the catkin class, the files are
now placed in the dbg package.