Downsides to colcon's --symlink-install option in ROS2?
Are there any downsides or pitfalls to using the --symlink-install
option in when building a workspace with colcon
in ROS2?
To me, it seems like a cross-the-board improvement; symbolic links instead of copies take less disk space, and make for faster development when using python
, urdf
, xacro
, yaml
, etc; and compiled language files are still handled as expected (to my knowledge). But I feel like I must be missing something, else I would expect colcon
to enable --symlink-install
by default if there weren't any downsides.