Shared Build Infrastructure

MCC's pinned RoModularBuild integration and ownership boundary.

Collaboration diagram for Shared Build Infrastructure:

MCC's pinned RoModularBuild integration and ownership boundary.

MCC consumes tools/RoModularBuild as a Git submodule pinned to a tagged revision. Initialize it after cloning:

git submodule update --init --recursive

Ownership

RoModularBuild owns project-independent mechanics:

• native compiler and generator preset bases;
• generic GNU Arm Embedded and AVR-GCC toolchains;
• configure, build, test, install, and clean workflow engines; and
• reusable CI composite actions.

MCC owns project policy:

• public preset names and MCC_* feature options;
• Foundation discovery and version compatibility;
• the MCC::MCC package, export, and downstream consumer validation;
• source modules, tests, examples, Doxygen, and release policy; and
• exact firmware, board, and hardware validation fixtures.

Adapters

Public commands under scripts/ remain stable. Thin adapters provide MCC's roots and option names to the shared engines. Local toolchain wrappers map the established MCC_* cache variables to the project-independent ROMODULAR_* variables before including the shared implementation.

This compatibility layer prevents the infrastructure migration from changing MCC's public presets, build directories, or cache interface. Debug and Release remain configurations of one platform preset.

Updating the Pin

Treat tools/RoModularBuild as read-only from MCC. Update its gitlink only as an explicit dependency change, pin a tagged revision, and rerun native, package-consumer, embedded compile/link, and documentation validation.