-
Notifications
You must be signed in to change notification settings - Fork 33
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 initial BuildStream backend #300
base: master
Are you sure you want to change the base?
Conversation
The generated elements do not yet include test dependencies and test suites of packages are not run as part of the build process.
Thanks for this contribution. Sorry for the delay. I am just ramping up as the new maintainer. I tested your modifications with the following steps:
And got the error:
Can you provide any guidance on what is supported? Cheers, |
External dependencies can be added to ros2-bst as needed without requiring changes in superflore. |
Thanks for the quick reply. Running the following completed successfully:
which updated the following files:
|
What are the future plans for the BuildStream backend? Will you or CodeThink be maintaining it going forward? Since ROS 2 Iron is now end-of-life, will you be adding support for Humble, Jazzy, or Rolling? |
This adds a generator for BuildStream elements. https://github.com/CodethinkLabs/ros2-bst is a working BuildStream project for a subset of ROS Iron where all elements for ROS packages have been generated by this branch of superflore. It also includes manually written elements for some external dependencies and depends on freedesktop-sdk for the base system and other external dependencies.
It currently cannot generate elements for all packages of a ROS distro as some packages require additional external dependencies. It's thus necessary to invoke superflore-gen-bst with the --only option to specify the target packages. Elements are also generated for internal dependencies of target packages.
The generated elements currently do not include test dependencies and test suites of packages are not run as part of the build process. This should be added as a future enhancement.