ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I'm not sure how others feel, but I see this usage as incorrect. You should not be deploying a catkin workspace like this, IMHO.
I do have an idea that could bring the desired affect, however. I think it would be best to try vcs
out.
On first machine:
cd catkin_ws
vcs export src > catkin.repos
On the second machine:
mkdir -p catkin_ws/src
cd catkin_ws/src && catkin_init_workspace
cd ..
vcs import src < catkin.repos
catkin_make
this will get you the contents of the other workspace in something you can just host as a GitHub gist.
2 | No.2 Revision |
I'm not sure how others feel, but I see this usage as incorrect. You should not be deploying a catkin workspace like this, IMHO.
I do have an idea that could bring the desired affect, however. I think it would be best to try vcs
out.
On first machine:
cd catkin_ws
vcs export src > catkin.repos
On the second machine:
mkdir -p catkin_ws/src
cd catkin_ws/src && catkin_init_workspace
cd ..
vcs import src < catkin.repos
catkin_make
this will get you the contents of the other workspace in something you can just host as a GitHub gist.
If you're not interested in deploying source, you can try deploying .deb
files instead, following this answer.