PoC: building Autoware with Pixi + robostack #7050
Unanswered
VRichardJP
asked this question in
Ideas
Replies: 1 comment 1 reply
-
|
@VRichardJP Nice work! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I see there is recently a lot of traction about pixi and robostack:
It does not seem anyone has proposed a way to build Autoware with pixi yet. I was bored so I decided I would try. I have managed to build almost all autoware packages, except for rviz plugins (broken), cuda packages (not detected) and tests (didn't try).
You can try it out on this fork: https://github.com/VRichardJP/autoware/tree/feat_pixi_build. See https://github.com/VRichardJP/autoware/blob/feat_pixi_build/README_PIXI.md for setup details.
While pixi and robostack are promising, I find there is currently a lot of (unecessary) integration friction:
ros2-distro-mutex, which imposes newer library versions than what is normally available in native ROS setups, for example PCL 1.15 and Boost 1.88. This is the cause of a lot of compilation errors, as many parts of the autoware codebase rely on deprecated features which have been removed in newer library versions. I had to update the code. See https://github.com/VRichardJP/autoware/tree/feat_pixi_build/patchesros2-distro-mutexmismatch), so I imported and built them along autoware (seerepositories/pixi.toml).Beta Was this translation helpful? Give feedback.
All reactions