ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Catkin Workspace Appending Workspace to End of ROS_PACKAGE_PATH [closed]

asked 2013-11-05 04:19:31 -0500

David Lu gravatar image

updated 2013-11-05 04:19:51 -0500

After the latest update to hydro, I am having trouble with my ROS_PACKAGE_PATH. Instead of

/home/dlu/Robots/Catkin/hydro_nav/src:/opt/ros/hydro/share:/opt/ros/hydro/stacks

which allows me to use my custom source navigation, instead after sourcing /home/dlu/Robots/Catkin/hydro_nav/devel/setup.bash, I get

/opt/ros/hydro/share:/opt/ros/hydro/stacks:/home/dlu/Robots/Catkin/hydro_nav/src

Why has our lord Catkin forsaken me so?

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by David Lu
close date 2013-11-05 10:46:58

Comments

Can you please provide a sequence of commands which reproduce the problem?

Dirk Thomas gravatar image Dirk Thomas  ( 2013-11-05 06:29:32 -0500 )edit

What version of catkin?

William gravatar image William  ( 2013-11-05 06:37:29 -0500 )edit

I apologize for the inconvenience. Despite replicating it on two computers earlier, I cannot replicate it now.

David Lu gravatar image David Lu  ( 2013-11-05 10:46:39 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2013-11-05 06:24:03 -0500

teddybouch gravatar image

Weird. I have hydro as well, and when I call the setup.bash in my workspace it pre-pends it like you are looking to do. I also find it interesting that if I source /opt/ros/hydro/setup.bash again, I am left with only /opt/ros/hydro/share:/opt/ros/hydro/stacks and without my workspace path.

You can always add it manually:

export ROS_PACKAGE_PATH=/home/dlu/Robots/Catkin/hydro_nav/src:$ROS_PACKAGE_PATH
edit flag offensive delete link more

Comments

2

When you source a setup.* file since Groovy it will always overwrite your environment. The environment of your workspace uses the environment which was set when you invoked CMake the first time and prepends the workspace specific paths.

Dirk Thomas gravatar image Dirk Thomas  ( 2013-11-05 06:28:49 -0500 )edit
2

Setup files for catkin *set* the environment, they do not *extend* the environment. To get that behavior you need to do `source setup.bash --extend`. With catkin workspaces you should only ever need to source one thing, the end of your workspace chain.

William gravatar image William  ( 2013-11-05 06:30:54 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2013-11-05 04:19:31 -0500

Seen: 525 times

Last updated: Nov 05 '13