| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I just finish working a project in ROS.
What I want to do actually is to make my package useful for another people, my package contain a node and big library. Like when I give the package to someone, he can use it without any problem.
So the question is how can I take the package to another computer and what should do in it so that the package works fine ?
(I'm using catkin package.)
Just copy-paste your project (the folder catkin_workspace/src/project) into the other person's catkin_workspace/src folder. Go to the top level catkin_workspace directory and hit catkin_make.
That is all that is needed. (Of course, assuming all dependencies, ROS and external, are satisfied.)
It is nice to use git-github. So that everything becomes easy.
Have a great day!
Git is a version control software. You can find tutorials here: http://www.vogella.com/tutorials/Git/article.html. The top level catkin_workspace is the directory from where you type catkin_make. It is the directory that has src, devel, build and CMakeLists.txt
If you want to publish your package for other developers in the community to use and contribute to, the first thing to do is to make the source code freely available for download. If you don't already have version control, https://github.com is usually a good choice. The recommended repository useage page on the wiki has some good guidelines on how to use github effectively with ROS.
Once you have your package available for download, the next step is to add it to the repository index and create a wiki page with some basic documentation about how to use your package.
The Getting Involved page on the wiki has some more general information about participating in the community that you may find interesting as well.
Asked: 2014-07-25 03:03:15 -0500
Seen: 356 times
Last updated: Jul 25 '14
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
So what's your question?
the question is clear but anyway I just add one