Configuration record hierarchies

A typical makefile has a hierarchical structure.

A typical makefile has a hierarchical structure. Thus, running clearmake or omake once to build a high-level target can cause multiple build scripts to be executed and multiple CRs to be created. Such a set of CRs can form a configuration record hierarchy, which reflects the structure of the makefile (see the following figure).

Figure 1. Configuration record hierarchy
hierarcy

An individual parent/child link in a CR hierarchy is established in one of two ways:

The catcr and diffcr commands have options for handling CR hierarchies:

Some ClearCase® features process entire CR hierarchies automatically. For example, when the mklabel command attaches version labels to all versions used to build a particular derived object (mklabel -config), it uses the entire CR hierarchy of the specified DO. Similarly, ClearCase maintenance procedures do not scrub the CR associated with a deleted DO if it is a member of the CR hierarchy of a higher-level DO.