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

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

* Use configuration options instead of patches
* Use relative paths in CMake installation files
* Use catkin class

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

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

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

using BBCLASSEXTEND = "native" and removing the separate native package files (thanks to Stefan Herbrechtsmeier for this hint)

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

copied the open issues from the ISSUES file to the github tracker and removed the ISSUES file (issue #13)

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