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

Add Iron support (based on iron/20240327) #3

Draft
wants to merge 3 commits into
base: humble
Choose a base branch
from

Conversation

gavanderhoorn
Copy link
Collaborator

@gavanderhoorn gavanderhoorn commented Jul 1, 2024

This builds, but needs (more) testing with MotoROS2.

Requires corresponding changes to _buildscripts.

NOTE: this does not (yet) track upstream HEAD of relevant Iron-related branches. It's slightly older.

Main outstanding issue: access to remapping argument parsing functionality has changed significantly in upstream micro-ROS (so much as to break our build). See Yaskawa-Global/motoros2#52 for the discussion.

Opening as draft, as we'd probably want to update this to track upstream more / use a more recent Iron (patch) release.


Edit: builds of MotoROS2 will need Yaskawa-Global/motoros2@main...gavanderhoorn:iron_no_remap_rules.


Edit 2: test build: micro_ros_motoplus_yrc1000-iron-20240327-rc0_1719833791.zip

@gavanderhoorn
Copy link
Collaborator Author

Note: this does not include #2 (need new patches for Iron).

@jimmy-mcelwain
Copy link
Collaborator

@gavanderhoorn I have a local commit with the updated upstream versions of these branches for iron. Would you like me to push that?

@gavanderhoorn
Copy link
Collaborator Author

Perhaps a PR against iron_update_20240327? So we can review the updates independently?

@ted-miller
Copy link
Collaborator

[iron_update_20240327](https://github.com/Yaskawa-Global/micro_ros_motoplus/tree/iron_update_20240327) appears to be working well. It passes all our tests.

I assume that we should just close this PR and rename iron_update_20240327 to iron

@gavanderhoorn
Copy link
Collaborator Author

I assume that we should just close this PR and rename iron_update_20240327 to iron

I would actually suggest to branch off a new iron branch from current HEAD of humble, update the target of this PR to be that new iron branch and then we could merge it.

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

Successfully merging this pull request may close these issues.

3 participants