Build script

An object that a builder uses in transforming inputs to outputs; it is essentially a binding between TeamConnection and a transformation tool, such as a linker or compiler. In OS/2, Windows, UNIX, or MVS/OE environments, a build script is usually a command ®le, but it can be a string that calls the tool. In MVS, it is a ®le containing JCL-like instructions.

Parser A tool that can read a source ®le and report back a list of dependencies of that source ®le. It frees a developer from knowing the dependencies one part has on other parts to ensure a complete build is performed. For example, a C parser can read a C source code ®le and report back a list of the ®les included by the source ®le or by the included ®les.

TeamConnection will re-verify all parser dependencies:

1.When the user creates or checks in the part, TeamConnection will add all parser dependencies that it can ®nd.

2.During build, TeamConnection will again check all parser dependencies and update as needed.

Parent-child relationships in a build tree

One relationship that is important to understand and distinguish is the relationship between parent and child parts in a build tree.

Though parent-child relationships usually imply that the parent part generates the child part, in a TeamConnection build it is the opposite. Because TeamConnection places the build output at the top of the tree, it refers to the build output as the parent and to the build input as the child.

A child part can be related to a parent part one of three ways: it can be an input part, an output part, or a dependent part.

Input parts

A part used as direct input to your build. An example of this is a C language source part. If you start a build and this part has changed, the changed part will be part of the new build.

Output parts

A generated output from a build, such as an OBJ or EXE part, or a part with no contents that serves as an organizer object. If you start a build and this part has changed, the changed part will be included in the new build.

Dependent parts

A part needed for the build operation to complete but that is not passed directly to the compiler. An example of this is an include part. If you start a build and this part has changed, the changed part will be included in the new build.

Chapter 10. Basic build concepts 131

Page 151
Image 151
IBM SC34-4499-03 Parent-child relationships in a build tree, Build script, Input parts, Output parts, Dependent parts