Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make meta-ros layer compatible with kirkstone yocto version #999

Closed
freallearn opened this issue Apr 27, 2022 · 6 comments
Closed

Make meta-ros layer compatible with kirkstone yocto version #999

freallearn opened this issue Apr 27, 2022 · 6 comments

Comments

@freallearn
Copy link

No description provided.

@shr-project
Copy link
Contributor

I no longer maintain this layer, but @moto-timo has few changes to make this compatible https://github.com/moto-timo/meta-ros/commits/kirkstone

Future maintenance of meta-ros was discussed in OSRF TSC https://discourse.ros.org/t/ros-2-tsc-meeting-january-20th-2022/23986/3 , but I haven't seen any update since then (I don't follow discourse very closely).

@shr-project
Copy link
Contributor

#1009

@bchoineubility
Copy link

Hi,

I nearly can build ros-image-core with moto-timo/meta-ros but, ros-image-world.

Maybe, it would be not tried in kirkstone and yocto yet.

please, if there are any update for it.

BR,
Mark

@robwoolley
Copy link
Collaborator

I just pushed support for Noetic, Humble, and Iron to the kirkstone-next branch. It builds with ros-image-core and getting ros-image-world working is desirable. Any feedback you have would be valuable. I encourage you to file issues with anything you find.

Regards,
Rob

@bchoineubility
Copy link

@robwoolley Many thanks for this release.

May I use kirkstone branch instead of kirkstone-next ?

BR,
Mark

@robwoolley
Copy link
Collaborator

Yes, you can. Both branches match at the moment.

I also just created a PR for Humble-Kirkstone that fixes the ROS packages to fix build failures when building for 64-bit machines: #1057

I intend to merge it once I do more testing to make sure I haven't broken anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants