| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi, have a package with one cpp file, worked great. added another cpp file and built the workspace, now rosrun can't locate the package any more.
when creating the package I have implemented this command echo "source ~/catkin_ws/devel/setup.bash" >> ~/.bashrc , and have tried rospack profile which didn't list the path. why does this happen please?
I had my VM paused from yesterday, turned PC on, resumed VM, opened one terminal, typed roscore, opened another one, typed rosrun package_name, hit tab key twice and the exe appeared.
Every time you open a new terminal, a new bash session is started.
if you have your .bashrc setup to do source ~/catkin_ws/devel/setup.bash for you, then new terminals will cause your workspace to be sourced.
If you add a package, build your workspace, then don't source it, the package will not be found.
If you now open a new terminal - as you say you did - that terminal will start a new bash session, causing your workspace to be sourced. And as the new package has now been built, it will be added to the appropriate environment variables and can then be found - in the new terminals - by rosrun and roslaunch.
For already open terminals (really: bash sessions), just source ~/catkin_ws/devel/setup.bash yourself, and new packages should now be found.
Edit: some related questions:
Thanks gvdhoorn, in my .bashrc, at the very bottom, I can see the source link to the package, as you're describing. In case this happenes again, I'm more than happy to write how I fixed the issue. But from what I understood, as long as the .bashrc has the source link, there shouldn't be any issues.
in my .bashrc [..] I can see the source link to the package
Just to be extra clear: the source line points to the devel space, not to any package.
It can't, because package directories do not contain the necessary files.
Asked: 2018-01-11 09:00:14 -0500
Seen: 153 times
Last updated: Jan 12 '18
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.
Please edit your question to provide more information. There's not enough here to reproduce your problem. Please provide the full context of commands you're running with their outputs and any debugging commands you're trying as well.
Hi tfoote, There is not much I can add.
1. (terminal 1) catkin_make <- builds 100%
2. (terminal 2) roscore
3. (terminal 3) rosrun package_name <- double tab doesn't resolve path
Do you do a
source ~/catkin_ws/devel/setup.bashafter step 1? Your.bashrcis only evaluated when you open a new terminal, there is no magic there that makesbashupdate itself if/when you runcatkin_make.Without the
sourcestep,rosruncan't find your package.Hi gvdhoorn, so how come turtlesim works fine all the time?
Isn't this the magic trick:
echo "source ~/catkin_ws/devel/setup.bash" >> ~/.bashrcthat makesbashupdate itself evertimecatkinis run ?No. Again:
.bashrcis only evaluated (ie: read) when you start a new instance ofbash. That is typically only when you start a new terminal.See What is the purpose of .bashrc and how does it work? for some more info on that.
technical but: because the
turtlesimpackages were already present on theROS_PACKAGE_PATHwhen you started yourbashsession.Either in your
catkin_wsor in/opt/ros/$distro.And just to clarify: this is a "Linux thing", not something specific to ROS.
If you can confirm that things work after you
sourcethesetup.bashafter you built your workspace, I'll write an answer.