Resolves import error in __init__.py files derived from catkin/cmake/templates/__init__.py.in template,
e.g. in tf:
  File "/usr/lib/python2.7/site-packages/tf/__init__.py", line 7, in <module>
    from pkgutil import extend_path
ImportError: No module named pkgutil

The catkin recipe is updated to 0.5.77 to be in line with
https://github.com/ros/rosdistro/blob/ef3a7449d7f7ef6e691a5724ef6c485e75cfd4af/hydro/release.yaml.

The native packages are not required anymore, because the needed
python scripts during compile time are also provided by the
cross-compiled packages and the python scripts are platform
independent. Only the catkin package is provided as native package.

The catkin recipe was updated to 0.5.73 to be in line with
https://github.com/ros/rosdistro/blob/4551e7c32d1b34984410b79bc0ec36afe3d3d245/hydro/release.yaml.
The previously applied patch has been included in 0.5.73 and is
removed from the recipe and this repository.

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

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

The native catkin recipe has no runtime dependency on
the native version of packagegroup-core-buildessential.

The catkin scripts require the ast python module, which is shipped
with python-misc.

catkin is a build tool based on cmake and requires the common
build tools to work properly.

The catkin_make command requires a number of python modules.

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

Catkin require a .catkin file in all CMAKE_PREFIX_PATH to add them
to the CATKIN_WORKSPACES. Remove this requirement as it couldn't
be satisfy when catkin packages are installed into the common usr
prefix. Without this adaption catkin couldn't find all files.

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

The local version was replaced by a solution from a catkin
maintainer.

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

The catkin framework need some modification to support cross compiling
packages via yocto. When we want to upstream patches we need to provide
patches against the current groovy-devel branch. Use this branch as base
for our work to simplify the tests and to unify the developing process
of catkin.

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>

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