ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Assuming you're asking about best deployment strategies.
For us, we have a CI server that builds all our ros packages and zips the contents of the install directory into a build artifact. In projects that depend on that package, you can use something like vcstool to specify what packages to download, where to extract them to etc. This way you can provide a url to where your build artifact is and they can download it and extract it to the install directory
For item #3, when you run catkin_make install
it will (assuming your CMakeList.txt is configured properly) put build files into a install folder. You can copy the contents of that install folder and distribute that as needed. To use else where, you can merge the install folder from your common package with the install dir in your competition install dir. Be sure to source the install directory instead of the devel directory.