You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the noetic-devel branch, resolving substitution arguments was outsourced to roslaunch. This resolves $(find) after other arguments like $(arg) (see here), which means I do things like pass $(find) into an argument. For example:
and then I could pass in something like robotfile:=$(find mypkg)/urdf/robot.urdf.xacro, and expect the included filename to ultimately be resolved properly through the $(arg) and $(find).
On the ros2 branch, this logic has been changed so that the above no longer works for me. I'm wondering if this change was intended, or if I'm just doing something wrong here.
The text was updated successfully, but these errors were encountered:
Thanks, that does it! I don't actually need a release; I came across this while working on xacrodoc, which is a small tool that modifies xacro to (1) have more support for programmatically compiling files, and (2) makes the package-lookup mechanism fully functional even without ROS.
On the
noetic-devel
branch, resolving substitution arguments was outsourced to roslaunch. This resolves$(find)
after other arguments like$(arg)
(see here), which means I do things like pass$(find)
into an argument. For example:and then I could pass in something like
robotfile:=$(find mypkg)/urdf/robot.urdf.xacro
, and expect the included filename to ultimately be resolved properly through the$(arg)
and$(find)
.On the
ros2
branch, this logic has been changed so that the above no longer works for me. I'm wondering if this change was intended, or if I'm just doing something wrong here.The text was updated successfully, but these errors were encountered: