The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Hi, hopefully this helps you out.
From my personal experience (on Ubuntu) I've found that adding the following lines to my ~/.bashrc file keeps everything for me in working condition:
source /opt/ros/fuerte/setup.bash
export ROS_PACKAGE_PATH=~/ros_workspace:$ROS_PACKAGE_PATH
export ROS_WORKSPACE=~/ros_workspace
and in your case I think you would want it to be:
source /opt/ros/fuerte/setup.bash
export ROS_PACKAGE_PATH=~/fuerte_workspace:$ROS_PACKAGE_PATH
export ROS_WORKSPACE=~/fuerte_workspace
That should let you use roscd and other ros command line tools with your setup.
| | 2 | No.2 Revision |
Hi, hopefully this helps you out.
From my personal experience (on Ubuntu) I've found that adding the following lines to my ~/.bashrc file keeps everything for me in working condition:
source /opt/ros/fuerte/setup.bash
export ROS_PACKAGE_PATH=~/ros_workspace:$ROS_PACKAGE_PATH
export ROS_WORKSPACE=~/ros_workspace
and in your case I think you would want it to be:
source /opt/ros/fuerte/setup.bash
~/fuerte_workspace/setup.bash
export ROS_PACKAGE_PATH=~/fuerte_workspace:$ROS_PACKAGE_PATH
export ROS_WORKSPACE=~/fuerte_workspace
That should let you use roscd and other ros command line tools with your setup.
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.