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
I'm building ROS1 packages, e.g. moveit_calibration with colcon build --symlink-install. There we use versioned libraries: set_target_properties(${MOVEIT_LIB_NAME} PROPERTIES VERSION "${${PROJECT_NAME}_VERSION}")
However, this causes colcon to symlink libs into the wrong folder (package instead of package/lib) and w/o symlinking .so:
I can't transfer issues cross-organization, but this ticket belongs on ros/catkin. While colcon does tell catkin that it should use symlinks, the actual symlinking logic is implemented there.
I'm building ROS1 packages, e.g.
moveit_calibration
withcolcon build --symlink-install
. There we use versioned libraries:set_target_properties(${MOVEIT_LIB_NAME} PROPERTIES VERSION "${${PROJECT_NAME}_VERSION}")
However, this causes colcon to symlink libs into the wrong folder (package instead of package/lib) and w/o symlinking
.so
:When dropping the
VERSION
setting, but still performing a symlink install, it works:A
--merge-install
with versioned libs works as expected as well:So, it seems the only missing use case is versioned libs and a symlinked install.
The text was updated successfully, but these errors were encountered: