I'm trying to make our build compatible with catkin_make and catkin tools, but how CATKIN_DEVEL_PREFIX is handled in the two tools is causing me some trouble.
We have some (non-ROS) tools that generate headers that need to be included by the current package being built, and by downstream packages. Our pure-cmake build system would create these headers in the out-of-source build directory and install them into the install directory. Downstream packages would include the $INSTALL/include directory and all would be well. We adapted our build to be catkin_make compatible by copying the files into ${CATKIN_DEVEL_PREFIX}/include at configure time, and downstream packages could find them by adding ${CATKIN_DEVEL_PREFIX}/include to their include path.
This doesn't work with catkin tools, because CATKIN_DEVEL_PREFIX points to a devel/.private directory and then symlinks content into devel space. Is there a variable available at configure time in CMake that points to workspace/devel that is available in both catkin_make and catkin tools?
I know this problem can be solved by making foo-extras.cmake.develspace.in and foo-extras.cmake.installspace.in for each project, but that'll be a huge pain. A variable that is consistent between the two tools that points to the workspace/devel directory would be a lot more straightforward.
Thanks,
-Mark
↧