ROS 2 Lyrical currently has no grid_map entry in lyrical/distribution.yaml, so none of the ros-lyrical-grid-map-* packages are installable on Ubuntu Resolute. This blocks downstream Lyrical ports that previously consumed the Kilted binaries.
Could a Lyrical Bloom release be prepared from the ROS 2 branch once the current ROS 2 build fixes in #520 are resolved?
A local Lyrical build also exposes the newer ament target-linking transition in grid_map_ros: replacing the ament_target_dependencies(... SYSTEM ...) call with imported-target target_link_libraries is required with the Lyrical toolchain. I can submit that as a focused follow-up PR if it is not covered by #520.
The goal is to consume normal ros-lyrical-grid-map-core, ros-lyrical-grid-map-msgs, ros-lyrical-grid-map-cv, and ros-lyrical-grid-map-ros packages rather than carrying a downstream source build.
ROS 2 Lyrical currently has no
grid_mapentry inlyrical/distribution.yaml, so none of theros-lyrical-grid-map-*packages are installable on Ubuntu Resolute. This blocks downstream Lyrical ports that previously consumed the Kilted binaries.Could a Lyrical Bloom release be prepared from the ROS 2 branch once the current ROS 2 build fixes in #520 are resolved?
A local Lyrical build also exposes the newer ament target-linking transition in
grid_map_ros: replacing theament_target_dependencies(... SYSTEM ...)call with imported-targettarget_link_librariesis required with the Lyrical toolchain. I can submit that as a focused follow-up PR if it is not covered by #520.The goal is to consume normal
ros-lyrical-grid-map-core,ros-lyrical-grid-map-msgs,ros-lyrical-grid-map-cv, andros-lyrical-grid-map-rospackages rather than carrying a downstream source build.