# Will intrinsic supports ros2 on bazel with bzlmod?

**URL:** <https://discourse.openrobotics.org/t/will-intrinsic-supports-ros2-on-bazel-with-bzlmod/50890>\
**Category:** ROS General\
**Tags:** ros2\
**Created:** [November 9, 2025, 7:18am UTC](https://discourse.openrobotics.org/t/will-intrinsic-supports-ros2-on-bazel-with-bzlmod/50890 "2025-11-09T07:18:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wep21](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/wep21/32/12192_2.png) [@wep21](https://discourse.openrobotics.org/u/wep21)\
**Post date:** [November 9, 2025, 7:18am UTC](https://discourse.openrobotics.org/t/will-intrinsic-supports-ros2-on-bazel-with-bzlmod/50890/1 "2025-11-09T07:18:45Z")

</div>

I found out intrinsic hosts their own bzlmod registry for ros2 core packages.

Will intrinsic supports ros2 on bazel with bzlmod officially?

> **[ROS Central Registry](https://intrinsic-opensource.github.io/rcr-ui/)**

> **[GitHub - intrinsic-opensource/ros-central-registry: A central registry containing Bazel modules for...](https://github.com/intrinsic-opensource/ros-central-registry)**
>
> A central registry containing Bazel modules for ROS packages.

---

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [November 10, 2025, 4:44am UTC](https://discourse.openrobotics.org/t/will-intrinsic-supports-ros2-on-bazel-with-bzlmod/50890/2 "2025-11-10T04:44:58Z")

</div>

⚠ This is an experiment and and work in progress. You’re welcome to try it and we would appreciate feedback. However it’s a proof of concept with pinned forks of packages for prototyping and definitely not stable. ⚠

Also the main developer for this prototype is on leave until the end of the year so please be patient.

For more information please see the tracking issue here with some recent updates:

> <https://github.com/ros2/ros2/issues/1726>
>
> Using bazel as one of the potential build systems for ROS 2 would have a lot of …benefits. Bazel provides some use cases which are relevant. For example traceability and/or reproducible builds. There are already some open source projects which tackle this:
> 
> https://github.com/ApexAI/rules\_ros
> https://github.com/mvukov/rules\_ros2 
> https://github.com/RobotLocomotion/drake-ros/tree/main/bazel\_ros2\_rules 
> 
> If possible we should find a way to unify these different projects and support just one Bazel rules.
> 
> We need to consider the following points:
> 
> Taking in account the previous point about decoupling ROSIDL from CMake, we need to ensure that the ROSIDL changes enable straightforward message generation for other build systems.
> Develop and support official or community-driven Bazel rules for building ROS 2 workspaces and packages.
> Provide examples and guidance for structuring and building complex ROS 2 projects using Bazel.
> 
> PMC PoC: @asymingt

And there’s discussion of standing up a new Bazel working group in the ROS PMC see the notes from Nov 4th:

> [@ROS PMC Minutes for November 4, 2025](https://discourse.openrobotics.org/t/ros-pmc-minutes-for-november-4-2025/50825):
>
> The [ROS PMC](https://osralliance.org/staging/wp-content/uploads/2024/03/ros_project_charter.pdf) meeting for this week was on Tuesday. The notes from the meeting are available at [ROS PMC weekly meeting agenda](https://docs.google.com/document/d/1TGXYp33N00ZJtilsRzfClFXcSyMa4QKVNmA03Lx9D7w/edit?tab=t.0#heading=h.g1vwn2803btt)ROS PMC Business Ending mentorship periods Just a note to @mjcarroll that we need to follow up and close out any outstanding Committer mentorship periods. Potential new PMC members [mjcarroll] @InvincibleRMC - sending formal announcement today. Potential new Working Groups ROSGraph from @emersonknappPacking and Infrastructure Maybe direct people to Infrastructure…

If you’re interested I would recommend connecting with the ROS PMC and potentially volunteering with the Bazel working group.