-
Notifications
You must be signed in to change notification settings - Fork 26
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
Adding new build type #24
Comments
This package currently doesn't contain any of the actual build / test logic. I only dispatches (based on the package build type) to an extension provided by other packages (e.g. CMake or Python). For Cargo that could be done the same. If |
Understood, this has been done in #25 |
#31 refactored the code in this package and uses extensions for each build type. That enables to contribute support for other build types from any Python package (rather than requiring changing this package. Please see the changes in the referenced PR for examples how that is done. With this in place I would suggest to provide support for other build types through separate packages (rather than this package). One advantage is that the maintainer of that package has full control when / how to release changes. Also this package is also available as a Debian package (beside PyPI) so all dependencies need to also provide Debian packages which is not always feasible (since the ROS apt repositories require permission to push new Debian packages which can't easily be granted to more people 😟). |
I will go ahead and close this ticket since the original question seem to have been answered. Please feel free to comment on the closed ticket. |
I'm wondering if ROS support for new build types (let's say Cargo builds for Rust support) should be added to this repository or to a new one (colcon-ros-cargo?).
The text was updated successfully, but these errors were encountered: