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
This isn't currently supported but it would be convenient; opening for visibility/tracking.
e.g. if I have an ament_python package, when I swap to installing with symlink, a launch invocation that was otherwise successful then gives:
$ ros2 launch topic_monitor launch_reliability_demo.launch.py
file 'launch_reliability_demo.launch.py' was not found in the share directory of package 'topic_monitor' which is at '/Users/dhood/ros2_ws/install_isolated/topic_monitor/share/topic_monitor'
The text was updated successfully, but these errors were encountered:
The real issue was with the setup.py of the package that was symlink installed. It actually wasn't installing properly but giving this error:
Installed /Users/dhood/ros2_ws/build_isolated/topic_monitor
running install_data
error: can't copy 'launch/fragmentation_demo.launch.py': doesn't exist or not a regular file
which was because I had listed the launch files as data_files that were stored in the source directory of the python package. Moving them out of the directory, installation works, and then the launch file can be run.
I haven't managed to make the launch files actually get installed as symlinks yet, but that's not the fault of ros2 launch, so I'll close this.
This isn't currently supported but it would be convenient; opening for visibility/tracking.
e.g. if I have an
ament_python
package, when I swap to installing with symlink, a launch invocation that was otherwise successful then gives:The text was updated successfully, but these errors were encountered: