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

Proposal: switch to shorter names for MotoROS2 binaries #109

Merged
merged 2 commits into from
Aug 3, 2023

Conversation

gavanderhoorn
Copy link
Collaborator

The main change is in f44a537: it updates the VS project to change the names of the .out files to their shorter alternatives as discussed in #107.

See the commit comment for the naming scheme used.

The second commit updates the readme to refer to the binaries by their new names.

@gavanderhoorn
Copy link
Collaborator Author

@ted-miller: this uses m for the YRC1000micro, mimicking the .yrcmLib extension.

That's different from what we currently use for the micro (motoros2_yrc1000u_humble.out). I don't really have a preference, so we could change it to u if you'd prefer.

This will help loading these binaries on older controllers, such as the DX200, while still being reasonably clear as to what controller series and ROS 2 version are supported by each file.

Naming convention: mr2_<controller>_<ros2_codename>.

Where 'mr2' is the abbreviated application name ('MotoROS2').

And where <controller> is the abbreviated name of the controller series: 'fs' (FS100), 'dx2' (DX200), 'yrc1' (YRC1000) and 'yrc1m' (YRC1000micro).

And where <ros2_codename> is the first letter of the ROS 2 codename: 'f' (Foxy), 'g' (Galactic), 'h' (Humble), etc.
Copy link
Collaborator

@ted-miller ted-miller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you going to do this on the DX2 PR too?

@ted-miller ted-miller merged commit c284c12 into main Aug 3, 2023
10 checks passed
@ted-miller ted-miller deleted the shorter_binary_names branch August 3, 2023 19:01
@gavanderhoorn
Copy link
Collaborator Author

Are you going to do this on the DX2 PR too?

I'll rebase #49 and add the missing changes there.

We need to review the readme and other files for missing DX200 references a final time anyway.

gavanderhoorn added a commit that referenced this pull request Aug 4, 2023
gavanderhoorn added a commit that referenced this pull request Aug 23, 2023
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.

2 participants