Alternatives for (not working) nested substitution arguments for roslaunch
I´m currently changing the launch file setup on a project and would like to do something like
<include file="$(find $(env ROBOT_TYPE)_config)/launch/planning_config.launch">
This doesn´t appear to be possible. There is a workaround by creating one launch file per robot type and referencing that, but I was wondering if there are other options that I missed and that do not require creating one launch file per robot type. I´m hoping I´m missing some otherwise obvious simple alternative here ;)
add a comment
