Revision history [back]

I was able to resolve this, by restructuring the include folder as follows:

And reducing the install tags to ` install(DIRECTORY include/cav_driver_utils/ DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION} )

` I can understand why this approach is supported by both catkin_make and catkin_make_isolated as it follows the recommended include folder structure in ROS, but I do not understand why it seems this structure was required by catkin_make but not catkin_make_isolated. I would have thought that the install tags were primarily a CMake concept and wouldn't be impacted by the build tool in this way. Feel free to enlighten me in the comments. In the meantime I am marking this issue as resolved.

I was able to resolve this, by restructuring the include folder as follows:

And reducing the install tags to ` to

install(DIRECTORY include/cav_driver_utils/ DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION} )

` I can understand why this approach is supported by both catkin_make and catkin_make_isolated as it follows the recommended include folder structure in ROS, but I do not understand why it seems this structure was required by catkin_make but not catkin_make_isolated. I would have thought that the install tags were primarily a CMake concept and wouldn't be impacted by the build tool in this way. Feel free to enlighten me in the comments. In the meantime I am marking this issue as resolved. resolved.