This page discusses the RootPath, the trees of the QEF approach, and introduces the software process that they supports. |
|
In the previous page's description of the qdsrv records, the eighth field is called the "RootPath" and the RootPath in record #46 contained three directories:
/g/dt/cook/obj /g/dt/cook/work /p/cook/s3.4These are the root directories of the object tree, working tree, and the baseline (i.e., source) tree. The QEF approach normally uses five types of trees.
Supplementary notes regarding trees |
| To change source, the developer fetches a copy of the file or files to be changed from the *VS system and stores writable copies in the working tree. The QEF's SrcPathing mechanism ensures that the developer's source file will take precedence over the baseline version. Note that a working tree does not have to have all the directories of the baseline. Only those directories required to hold changed source are necessary. Similarly, a developer's object tree need not duplicate the full directory structure of the baseline. QEF's multi-directory management mechanism will compensate for missing directories. The developer's product as built from a partial object tree will also be partial. The product built by production will be searched for any files (e.g., headers, libraries, tools) that are not built by the developer. |
cook14.qh - 1.16 - 05/09/23 |