Extending meta-ros with ros2 + openembedded (yocto)

Hey all,

not sure if this is the right place for it or if I should jump over to discord. We have our own ros2 workspace extending kilted that we’d like to include in our yocto image. Is there a preferred way for creating the receipes - and if so how? After a bit of looking around it seems there’s superflore but I’m not sure if it is intended for use outside of meta-ros.
It seems like the other option is to manually create the receipes for each package in our workspace based off the autogenerated ones?
Is there a third option I am missing?

Thanks in advance,
Nico

Hi @zarmomin,

Sorry for the delayed response. I missed this while getting ready for ROSCon.

There is a brand new tool that I created that will discover packages in a colcon workspace and write Bitbake recipes based on the package.xml files and the git repository information.

So far, I have used it to create and build recipes for Space ROS Jazzy (~ 220 packages). Your use case is something I want to support, so I would be interested in helping you try it out.

I’m just catching up from everything I missed while in Singapore. Feel free to reach out to me here on Discourse or on Discord or Zulip. There is a Community Groups > OpenEmbedded category that you may use. Our next ROS OpenEmbedded Community Group meeting is also on Monday: ROS OpenEmbedded Community Group - Meeting #44: 2025/11/10 @ 4pm UTC - Community Groups / OpenEmbedded - Open Robotics Discourse

Regards,
Rob

2 Likes

Hi @robwoolley

This tool sounds exactly like what I need. Is it something you can share, or is it available online somewhere?
Best Christian

Hi,

I pushed a beta release of the Python application to GitHub - robwoolley/mash

I tested it with the ROS 2 tutorials and demos git repositories as well as Space ROS. The README.md has step-by-step instructions showing it working.

I am happy to take feedback on use cases where it doesn’t work. I know that it will not work if the ROS package isn’t backed by a git repository. I would love to get feedback on enhancements folks would like to see to cover different use cases. GitHub Issues and pull requests are welcome as well.

Regards,
Rob

1 Like