This page explains:
- How to build EasyNav packages for ROS 2 jazzy using this repo (Pixi + Vinca + rattler-build).
- How to consume the resulting packages in a separate colcon workspace (Pixi template).
- Producers (package creators): build
.condaartifacts into a local file-channel atros-jazzy/output/. - Consumers (users): create a normal ROS 2 workspace and install dependencies from that local channel.
From the ros-jazzy/ folder:
- Install the build environment:
pixi install
- Build the EasyNav subset (generate recipes → build → index):
pixi run easynav-all
Artifacts should land under:
ros-jazzy/output/linux-64/
Index files should exist under:
ros-jazzy/output/linux-64/repodata.json
- If a downstream Pixi solve says “No candidates found…”, clear repodata cache:
pixi clean cache --repodata -y
- The channel root is
.../ros-jazzy/output(not.../output/linux-64).
A ready-to-edit Pixi template is in:
ros-jazzy/irl-docs/easynav/pixi.tomlros-jazzy/irl-docs/easynav/activate.sh
- Create a workspace and copy the template files:
mkdir -p ~/ws/easynav_ws && cd ~/ws/easynav_ws- Copy
pixi.tomlandactivate.shfromros-jazzy/irl-docs/easynav/
- Enter the environment:
pixi shell
- Clone sources (example; adjust to your needs):
mkdir -p src && cd srcvcs import < easynav.repos
- Build:
pixi run build
- This template defaults to Zenoh:
export RMW_IMPLEMENTATION=rmw_zenoh_cpp
- Run the Zenoh daemon in a separate terminal:
ros2 run rmw_zenoh_cpp rmw_zenohd
- The consumer env pins
eigen < 5to reduce the chance of CMake falling back to system Eigen (/usr/include/eigen3) when building PCL-dependent packages.