removing RDEPENDS because we cannot check if it works as intended, as long as we are just compiling, but not running ROS.

gathering all packages in the meta package roscpp-core in the folder roscpp-core for better structuring

removing the ros prefix for the recipe of ROS' cpp_common package for uniformity and accepting the risk that the name cpp_common might clash when combined with other layers

adding the genmsg recipe, which is the first recipe that also creates some python modules and hence requires some more ingredients in the recipe

a metapackage is an empty package; switching from RDEPENDS to DEPENDS because it works, but it is not clear if that is really what I intend to express

adding the rostime recipe that relies on ros-cpp-common, trying to model the dependency of two ROS packages as dependency of two bitbake recipes

patching catkin to remove assertion for rt-library (this must revisited at some later point again when we have a better understanding of the issue.)

removing alternative recipe for catkin-native because using catkin and BBCLASSEXTEND+=native does the job for now

maybe it is also good to add the files in standard package to the development package in catkin (commented out because it is not clear yet if it does help eventually)

improving catkin-native, but it remains unclear what the difference between BBCLASSEXTEND += native and inherit native is and which one we should use.

adding dependencies that have been overseen when creating the image, but that are necessary if one builds catkin stand-alone

adjusting the README; a first try for cross-compiling the cpp-common things; extending the install-fuerte script

we patch catkin as catkin assumes that every linux is an ubuntu system but the openembedded linux system is not

catkin recipe missed to add the python modules to the packages (NB: QA still mentions so files not shipped)

improving catkin recipe so that it does run through (it compiles and installs now, but I am not sure if the installation is correct)