orocos-toolchain/rtt — pull request #22 by meyerj (2014-02-08 00:27:45+00:00)
Title: Re-enable auto-linking for catkin builds

With the current version of the `UseOROCOS-RTT.cmake` macro definitions I do not see a problem anymore to re-enable the auto-linking option (set the `OROCOS_NO_AUTO_LINKING` to `OFF`) also for builds that use catkin as a build tool. Using different default settings for this option depending on the build tool is not good practice and should be avoided if there is no very good reason to do so.

In the first versions of rtt adapted for catkin enabling auto-linking was indeed not a good idea as catkin also generates pkg-config files and the Orocos auto-linking feature used to generate huge linker command line as it could not distinguish between Orocos and non-Orocos packages. But especially since the introduction of the `OROCOS_ONLY` flag in 6c48b01c and the fact that auto-linking only acts on targets that are defined by the `orocos_*` macros since 4b7fc974 this should be solved now.

Furthermore I added the `OROCOS_ONLY` option also for dependencies parsed from the `manifest.xml` file in rosbuild and pure cmake packages. rosbuild packages can depend on catkin-packages and the rosbuild macros `rosbuild_add_*` already use the catkin-generated pkg-files to get compile and linker flags in this case (by invoking `rospack` internally). So the same reasoning why we need `OROCOS_ONLY` for catkin to avoid double linking applies to rosbuild, too.