typelib: Merge toolchain-2.7 and master branches for the 2.8 release

[meyerj]

The master and rock1408 branches of typelib diverged from toolchain-2.7 significantly (or vice-versa):

• toolchain-2.7...master
• master...toolchain-2.7

Which commits from which branch should be included in a new toolchain-2.8 branch for the upcoming release?

Related questions:

• utilrb: Merge toolchain-2.7 and master branches for the 2.8 release utilrb#10
• orogen: Merge toolchain-2.7 and master branches for the 2.8 release orogen#23

[doudou]

There are mainly two type of changes there:

• the ROS-specific stuff, which should now go on its own branch
• the OSX fixes which seem to already be on master. Typelib does not depend on utilmm anymore, and dyncall's has been ripped out, so quite a few OSX-related fixes are not needed anymore.

[meyerj]

I recently merged the master branch into toolchain-2.8 in 251439b in order to have the latest updates of package.xml. Can master be considered as stable or should this be reverted, so that toolchain-2.8 is based on rock1408 instead? I remember that there was a discussion about this, but I could not find it anymore.

The only differences between master and toolchain-2.8 are the updated version number in package.xml, the catkin env-hook for environment setup (which requires additional dependencies) and one additional header file to be installed (master...toolchain-2.8#files_bucket). Please review the changes and merge or cherry-pick to master whatever is reasonable.

Any objections against releasing the current toolchain-2.8 branch in ROS indigo?