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

catkin setup.sh overwrites PATH environment variable? [closed]

asked 2013-01-07 20:36:18 -0500

payneio gravatar image

I am following the groovy installation and tutorial.

I source /opt/ros/groovy/setup.bash in my .bashrc.

I then set up catkin workspace and run catkin_make.

The resulting devel/setup.bash, when sourced, eliminates the /opt/ros/groovy/bin reference that was in my PATH environment variable... meaning I can not continue with the tutorial which is about rospack.

Should the catkin workspace setup.sh be overwriting the PATH environment variable like this? The catkin manual says it should respect already-sourced script like /opt/ros/groovy/setup.bash, but it doesn't seem to be doing that.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by 130s
close date 2013-01-30 04:47:43

2 Answers

Sort by ยป oldest newest most voted
0

answered 2013-01-08 03:46:02 -0500

payneio gravatar image

Ahhh... I figured out what I was doing wrong. I had initially gone deeper into the documentation (as suggested) here: www.ros.org/wiki/groovy/Installation/Overlays

The process it explains was causing my failure:

$ mkdir -p ~/catkin_ws/src $ rosws init --catkin ~/catkin_ws/src /opt/ros/groovy $ cd ~/catkin_ws $ catkin_init_workspace $ catkin_make $ source ~/catkin_ws/devel/setup.bash

Even if I ensure /opt/ros/groovy/setup.bash was installed previously.

To get back on track in the tutorial, I deleted the ~/catkin_ws directory, re-sourced /opt/ros/groovy/setup.bash and just did the basic tutorial steps of: $ mkdir -p ~/catkin_ws/src $ cd ~/catkin_ws $ catkin_make $ source devel/setup.bash

edit flag offensive delete link more
3

answered 2013-01-08 00:10:37 -0500

KruseT gravatar image

I cannot reproduce your problem. Are you sure that after changing your .bashrc, you started a new terminal? Else the change in the .bashrc did not take effect, which would explain your error.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-01-07 20:36:18 -0500

Seen: 806 times

Last updated: Jan 08 '13