ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You can put that kind of export in your .bashrc
(or .zshrc
if you use zsh). Thus it will be automatically exported when you open a shell.
Check this page for more information.
2 | No.2 Revision |
You can put that kind of export in your .bashrc
(or .zshrc
if you use zsh). Thus it will be automatically exported when you open a shell.
Check this page for more information.information, as your problem is similary to having to run source /opt/ros/hydro/setup.bash
for each new shell.
3 | No.3 Revision |
You can put that kind of export in your .bashrc
(or .zshrc
if you use zsh). Thus it will be automatically exported when you open a shell.
Check this page for more information, as your problem is similary similar to having to run source /opt/ros/hydro/setup.bash
for each new shell.
4 | No.4 Revision |
You can put that kind of export in your
(or .bashrc~/.bashrc
if you use zsh). Thus it will be automatically exported when you open a shell..zshrc~/.zshrc
Check this page for more information, as your problem is similar to having to run source /opt/ros/hydro/setup.bash
for each new shell.
5 | No.5 Revision |
You can put that kind of export in your ~/.bashrc
(or ~/.zshrc
if you use zsh). Thus it will be automatically exported when you open a shell.
Check this page for more information, as your problem is similar to having to run source /opt/ros/hydro/setup.bash
for each new shell.
In your ~/.bashrc
, you will probably end up having something like this (if you use hydro):
# ROS
source /opt/ros/hydro/setup.zsh
export ROS_PACKAGE_PATH=~/catkin_ws:$ROS_PACKAGE_PATH