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 |
The argument pkg_arg get substituted by the absolute path to the package my_pkg which could for example be the string /home/user/ros/my_pkg. Hence rosbuild_add_roslaunch_check could check the current ROS_PACKAGE_PATH for the existence of this package and the file included.launch as roslaunch does when executing.
The value for the argument is determined by the current ROS_PACKAGE_PATH which can be checked offline in my opinion.
By the way, the behaviour is the same as hardcoding the argument to point to my_pkg:
<arg name="pkg_arg" default="/home/user/ros/my_pkg"/>
So why shouldn't it be possible to check this?
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.