Repository navigation
Conversation
Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
|
The Linux builds fail in 0.3.0 hardcodes So this PR needs the snapshot synced with rosdistro, which already has NavMap 0.6.0, EasyNav 0.5.0 and yaets 1.2.0. |
|
Covered in the RoboStack monorepo, RoboStack/robostack, where all ROS 2 distributions are now built. EasyNav, NavMap and yaets are in the shared package selection there on Linux, with the same 22 packages as here (RoboStack/robostack#76, RoboStack/robostack#79), and 🤖 Claude (AI assistant), on behalf of @Tobias-Fischer |
EasyNav 0.5.0 (with NavMap 0.6.0 and yaets 1.2.0) was released yesterday for Humble, Jazzy,
Kilted and Lyrical, and the rosdistro PRs are already merged. This PR selects its packages for
building, so they are built once the snapshot is synced with rosdistro:
vinca.yaml: the EasyNav, NavMap and yaets packages, including the new ones in 0.5.0(
easynav_recovery,easynav_simple_recovery,easynav_diagnostic_recovery,easynav_mhamcl_localizer,navmap_tools,easynav_nav2_bridgeand the PlayGrounds, except onHumble), in the Linux-only block as on Jazzy. On Jazzy,
easynav_gps_localizeris removed: it isno longer released.
robostack.yaml: rosdep keys these packages use that had no mapping here:python3-rich,python3-typing-extensionspython3-platformdirs,python3-richliboctomap-dev,python3-platformdirs,python3-rich,python3-typing-extensionsliboctomap-dev,python3-platformdirs,python3-richThe snapshot is not touched: these packages need the rosdistro snapshot that includes EasyNav 0.5.0.
All of them build with pixi-build-ros against these RoboStack channels, and we tested them in
simulation with the four PlayGrounds on Jazzy, Kilted and Lyrical (and Rolling).