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 |
You don't need any arcane magic such as artificial manifests. They set up an environment variable for that which you can set in your setup.sh. See the ros wiki for environment variables, and in particular ROS_LOCATION for more details.
| | 2 | No.2 Revision |
You don't need any arcane magic such as artificial manifests. They set up an environment variable for that which you can set in your setup.sh. See the ros wiki for environment variables, and in particular ROS_LOCATIONROS_LOCATIONS for more details.
| | 3 | No.3 Revision |
You don't need any arcane magic such as artificial manifests. They set up an environment variable for that which you can set in your setup.sh. See the ros wiki for environment variables, and in particular ROS_LOCATIONS for more details.details. e.g. in setup.sh:
export ROS_LOCATIONS="motors=/opt/diamondback/ycs/ycs_devices/motors"
After making sure the variable is set in my shell:
> snorri@snorriheim:/opt/diamondback$ roscd motors
> snorri@snorriheim:/opt/diamondback/ycs/ycs_devices/motors$ ls
actuator goo goo_firmware qgoo
Those listed by ls are actual ros packages, but it works equally as well on any directory outside your ros tree.
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.