In my robot application, I build one entrypoint package for the robot-side runtime (which is headless), and a different one for the development computer that I use to visualize and send commands.
However, with the ability to run x86 builds now, I can invoke two variations of this tool to create a docker runtime image and build those packages.
Right now, I have to change the defaults.yaml file in my workplace in between builds. Instead it would be nice to specify this via the commandline.
ros_cross_compile --colcon-defaults something.yaml, if the user doesn't specify then use defaults.yaml
Related Issues
N/A
Completion Criteria
User can expicitly specify the relative path of the colcon defaults yaml file within their workspace.
Implementation Notes / Suggestions
Add command line option
pass it to docker client constructor, use that or default value on None
Testing Notes / Suggestions
Add dependencies test with a non-default-named defaults file and make sure it is honored in the colcon list
Description
In my robot application, I build one entrypoint package for the robot-side runtime (which is headless), and a different one for the development computer that I use to visualize and send commands.
However, with the ability to run x86 builds now, I can invoke two variations of this tool to create a docker runtime image and build those packages.
Right now, I have to change the
defaults.yamlfile in my workplace in between builds. Instead it would be nice to specify this via the commandline.ros_cross_compile --colcon-defaults something.yaml, if the user doesn't specify then usedefaults.yamlRelated Issues
N/A
Completion Criteria
Implementation Notes / Suggestions
Testing Notes / Suggestions
Add dependencies test with a non-default-named defaults file and make sure it is honored in the colcon list