-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Initial OpenEmbedded support for rosdistro #20763
Conversation
Looks like the CI failure relates to the required dependencies. Please advise on the best way to proceed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great to see this coming in to add support for open embedded. I look forward to integrating this. However I'd like to suggest that we consider restructuring how we insert this to keep it more compact and maintainable.
ba0ea88
to
05aa348
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks with the update it looks good to me.
This can probably be landed independently/ahead of the other related PRs.
95d0540
to
ad3294b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can probably be landed independently/ahead of the other related PRs.
Makes sense to me.
@andre-rosa, looks like you're still tweaking things. Let us know when you believe this is ready to go in. |
Definitely will do, thanks for your review @tfoote @cottsay! |
5507a87
to
179c91b
Compare
42f024e
to
8d8a28f
Compare
47c23a8
to
584c3cd
Compare
@andre-rosa How far along is this PR? Is it ready for re-review? |
584c3cd
to
7f007ab
Compare
@allenh1 Currently, these entries support building ROS 2 Crystal for qemux86, qemuarm64 and raspberrypi3. |
a4fb097
to
67575d1
Compare
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
67575d1
to
c0d1431
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging these as is for crystal support and then iterating for further support sounds good to me. It will be one less step closer to being able to reproduce things without forks.
Sounds good to me -- we can improve ROS 1 support and, when dashing gets closer, dashing support in separate PR's. |
Initial OpenEmbedded support for rospkg ros-infrastructure/rospkg#166
Initial OpenEmbedded support for rosdep ros-infrastructure/rosdep#673
available from OE layer index at http://layers.openembedded.org
package @ meta-layer , where package resides in the OE meta-layer
https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401