We show a build system favouring the bottom-up composition of builds from developer contributions, instead of the top-down assignment of tasks.
The composition is progressively checked and validated. A special focus is directed to optimizing the checking of multiply used components.
The example uses C++ but the principle is general.