[Discourse.ros.org] [OpenEmbedded] Looking for meta-ros Maintainers

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Discourse.ros.org] [OpenEmbedded] Looking for meta-ros Maintainers

Chris via ros-users


I'm interested in porting Melodic to meta-ros. Do you have a tutorial on how to adapt the current indigo recipes to other versions?





---
[Visit Topic](https://discourse.ros.org/t/looking-for-meta-ros-maintainers/973/5) or reply to this email to respond.


If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
[hidden email]
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <http://lists.ros.org/mailman//options/ros-users>
Reply | Threaded
Open this post in threaded view
|

[Discourse.ros.org] [OpenEmbedded] Looking for meta-ros Maintainers

Chris via ros-users


Hi Lucas,

unfortunately we do not have a tutorial or extensive instructions on that yet, but I am happy to guide you through this. In fact, I was thinking about providing melodic myself, but I am currently still working on getting a new version on kinetic ready. So, it is good that you want to address melodic.

I suggest the following approach:

0. checkout my "kinetic-experimental-v4-work-in-progress-v1" branch; that is a snapshot of the latest kinetic branch that I am still working on.

1. update the ROSDISTRO and a few more places from kinetic to melodic.

2. run update-recipes.py (with my preliminary script-improvement patches) to produce all recipe updates

3. run `bitbake core-image-ros-world` and fix all build issues.

4. clean-up all your commits

For 1., you can look at the commit:

https://github.com/bulwahn/meta-ros/commit/1f1c2e1d03769d2bfe63e2ff42d72fade05e3cfb

You will simply need to update those places to melodic.

For 2., use the preliminary patches, which you can see at my branch "script-improvements-work-in-progress-v1", to update-recipes.py, to obtain the bash commands to generate the recipe update commits.

For 3., expect many packages to fail, many are probably simple issues,but only a few are really difficult to address.

I recommended to start your work on top of my kinetic-experimental-v4-work-in-progress-v1 branch, as I already resolved all except for one build issues for kinetic.

It would be best if you can share your branch on your fork in github, then I can have a look, test and help you with the build issues you encounter.

If you need any further help, let me know.


Lukas





---
[Visit Topic](https://discourse.ros.org/t/looking-for-meta-ros-maintainers/973/6) or reply to this email to respond.


If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
[hidden email]
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <http://lists.ros.org/mailman//options/ros-users>