adding roscpp-core recipe that shows how to turn a metapackage into a bitbake recipe
removing all roscpp_core packages from the created ros source archive
adjusting the core-image for ros-groovy
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
removing obsolete comment
replacing hard-code pathes with pathes set by bitbake's shell variables
the roscpp_core packages are empty at the moment, but should be created anyway
copied the open issues from the ISSUES file to the github tracker and removed the ISSUES file (issue #13)
adding the genmsg recipe, which is the first recipe that also creates some python modules and hence requires some more ingredients in the recipe
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
gathering all packages in the meta package roscpp-core in the folder roscpp-core for better structuring
the recipe ros-cpp-common is now simply called cpp-common
removing RDEPENDS because we cannot check if it works as intended, as long as we are just compiling, but not running ROS.
adding a number of recipes that build (on my machine)
another new recipe
using BBCLASSEXTEND = "native" and removing the separate native package files (thanks to Stefan Herbrechtsmeier for this hint)
adding a stub for our recipe creation script
adding a bunch of ros recipes, but they still come with a couple of unsolved issues
removing RDEPENDS in python-empy experimentally after using BBCLASSEXTEND = native
correcting license for roscpp-core (addressing issue #15)