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

install ament files by default #736

Merged
merged 1 commit into from
Jan 13, 2025
Merged

install ament files by default #736

merged 1 commit into from
Jan 13, 2025

Conversation

nim65s
Copy link
Collaborator

@nim65s nim65s commented Jan 13, 2025

@jorisv
Copy link
Contributor

jorisv commented Jan 13, 2025

I've got mixed feeling about this PR.

This will install this file in all our packages but this is only useful for ROS2 build system.
Did colcon setup some CMake variables to be able to recognize when we need to create ament_index file ?

@nim65s
Copy link
Collaborator Author

nim65s commented Jan 13, 2025

I don't understand your point.
Do you think a package installed from aur / brew / conda / nix / pip / robotpkg, should not be available for use in a ros workspace ?

Yes, a pair of useless files (one empty, and one with a single line) will be installed, but how big of an issue is this ? We are already installing package.xml all the time. And we have been installing those files in pinocchio for some time.

And for people who really don't want those 2 extra files, an opt-out option is still available.

edit: my bad, there are 3 files

@jorisv
Copy link
Contributor

jorisv commented Jan 13, 2025

I'm not an expert in ROS workspace.
I was thinking this file is only mandatory when building all our stack from source with colcon.

Also, is-it safe to mix binary package from aur / brew / conda /nix / pip / robotpkg with a ROS workspace ?
If it's a valid use case I don't have any problem with that.

@nim65s
Copy link
Collaborator Author

nim65s commented Jan 13, 2025

I think those files are used at runtime by ros tooling. So far we had no issues in our packages build by colcon without those files.

And yes, some mixes are unsafe, but there are plenty of safe ones. With aur / robotpkg, there are no unsafe options. Also, packages without binaries (eg. example-robot-data) are always safe.

@jorisv jorisv merged commit 6b0564f into master Jan 13, 2025
3 checks passed
@jorisv jorisv deleted the ament branch January 13, 2025 16:33
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