ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
First, switching a workspace from furete back to electric can always cause errors when compiling / building sources. Be aware of that. It is safer to create separate workspaces for different ROS versions.
Next, I suggest that you use rosws / rosinstall to create and manage your workspaces.
Third, open your .bashrc in some editor, and find any place mentioning ROS_ROOT, ROS_WORKSPACE, or setup.sh.
delete all those lines, there should only be one line in your .bashrc, that reads:
source ~/ros_workspace/setup.sh
2 | No.2 Revision |
First, switching a workspace from furete back to electric can always cause errors when compiling / building sources. Be aware of that. It is safer to create separate workspaces for different ROS versions.
Next, I suggest that you use rosws / rosinstall to create and manage your workspaces.
Third, open your .bashrc in some editor, and find any place mentioning ROS_ROOT, ROS_WORKSPACE, or setup.sh.
delete Delete all those lines, lines. Regarding ROS, there should only be one line in your .bashrc, that reads:
source ~/ros_workspace/setup.sh
Even if it can work, managing the ROS_PACKAGE_PATH yourself almost always leads to bad ROS_PACKAGE_PATH in the long run and confusing errors.
3 | No.3 Revision |
First, switching a workspace from furete fuerte back to electric can always cause errors when compiling / building sources. Be aware of that. It is safer to create separate workspaces for different ROS versions.
Next, I suggest that you use rosws / rosinstall to create and manage your workspaces.
Third, open your .bashrc in some editor, and find any place mentioning ROS_ROOT, ROS_WORKSPACE, or setup.sh.
Delete all those lines. Regarding ROS, there should only be one line in your .bashrc, that reads:
source ~/ros_workspace/setup.sh
Even if it can work, managing the ROS_PACKAGE_PATH yourself almost always leads to bad ROS_PACKAGE_PATH in the long run and confusing errors.