Thinking about this a bit more... while this is certainly possible, is it worth it?
Anyone doing ROS development will use the normal catkin workspace to build a ROS node. The ROS catkin stuff uses CMake, but presumably have their own layout and way of working, and way of deployment. So, there is probably no need for "embedding" a ROS workspace in this project. Anyone doing ROS can just compile a library generated from this project, and use cmake find_package to find this library. No need to confuse the issue by merging the two layouts.
Thinking about this a bit more... while this is certainly possible, is it worth it?
Anyone doing ROS development will use the normal catkin workspace to build a ROS node. The ROS catkin stuff uses CMake, but presumably have their own layout and way of working, and way of deployment. So, there is probably no need for "embedding" a ROS workspace in this project. Anyone doing ROS can just compile a library generated from this project, and use cmake
find_packageto find this library. No need to confuse the issue by merging the two layouts.