There are ~300 packages in the ROS2 distro. Some of them are host tools, like ament (no need to deploy on the target system), some are binaries installed on the target (libs etc.) and some are visualization tools like rviz (need graphics support, can stay on the host as well).
I build ROS2 for VxWorks and would like to cross-compile only packages that go to the embedded target.
I think such a split could be useful for the native compilation as well, e.g. when I don’t want to install everything on my target system.
Is it a way to separate them while building ROS2? Something like:
colcon build --host-tools (native build)
colcon build --target-binaries (cross or native build)
colcon build --graphic-tools (native build)
@dirk-thomas, probably you are the best person, who knows the answer