| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
There are a variety of old answers that walk through this process: #q252478 is one. You'll want to git clone https://github.com/ros-planning/navig... (package wiki pages usually link to the source repo pages) to put the source into a catkin_ws instead of using apt-get. If you source devel/setup.sh after building you'll be using the customized version of move_base instead of the one perhaps already installed with apt.
Maybe this works https://askubuntu.com/questions/28372... ? Even if it does I think a regular catkin_ws + git clone is more likely to be what they want, and is on the path to pushing changes back to github and pull requests.
Adding to this thread for future readers who may still have queries regarding this. There are 2 main ways of installing ROS packages: installing through Debian packages or installing through source. For example, if I were to download move_base for ROS kinetic, which is part of the navigation repository, I can do either of the 2 commands below:
Installing through Debian packages:
Installing from source:
Both of these would have installed the move_base package into your system. Debian packages are installed into /opt/ros/kinetic/... while Source packages are installed directly into your workspace which is catkin_ws/src in this case. The benefit of installing from source is that you can edit the source code however you feel like.
Of course if you have installed from Debian prior to this and would now like to install from source, you can simply perform the procedure to install from source and the source package will be overlayed on top of your Debian package which means ROS will look for the source package before looking for a Debian package
Additional source: https://industrial-training-master.re...
Asked: 2018-08-26 09:56:48 -0600
Seen: 1,753 times
Last updated: Jun 27 '21
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.
