Abstract

I follow the demo and present the code of the components building up the makefile system.

Every developer has his own focus and organizes his world around it. He takes care that the dependencies are satisfied from his point of view. Composition should not reuse his contribution as such.

One needs to ensure the consistency of the various contributions. This is best achieved by integrating continuously, and validating progressively the audited results. Labels make offer concrete milestones, and help to communicate.

• the derived objects are promoted so that they are not scrubbed right away
• the labels show the propagation of the dependencies
• they make it easy to reproduce the builds, and thus to assess the effect of changes

Checking is time consuming. As the composition will respect the dependency graphs produced by the individual developers, one needs an optimization to avoid that the same checks are performed several times:

• the build detects whether it is the top invocation or a child, logs its activity and propagates this information down to its children; if invoked again, it will find its own log and return directly
• care is taken that the house-keeping activity is not recorded in the build audit
• in the end, the top invocation cleans up any trace of the logging activity.

The method is not intrusive: we avoid the need for a top-down navigation, and ensure that the results of the developers' builds may be promoted and reused for other components and the integration build.