To use the builder from a previous release, you can link to a part that uses it in that release. This action copies the builder to the new release. Otherwise, you must create the builder again in the new release.
Script, File type, and Source ®le
These ®elds work together to de®ne the build script that the builder invokes to
accomplish the transformation. (The File type ®eld on the GUI corresponds to -text, -binary, and -none in the command. The Source ®le ®eld on the GUI
corresponds to the -from attribute.)
v If the build script is simple enough to be expressed in one line, you can
specify it in the Script attribute when you create the builder, and specify a ®le type ofnone. At minimum, the script must specify the name of the
transformation tool. For example, to invoke the C Set/2 compiler, you might specify these values:
± File type - none
± Script - icc
See ªWriting a simple build scriptº on page 153 for more information.
v If the build script is more complex, you must ®rst create a separate ®le containing it; see ªWriting an executable ®le for a build scriptº on page 153
for more information about how to write it. Specify the fully quali®ed path name of your ®le as the source ®le, and specify the ®le type textas or binary. TeamConnection can also detect the ®le type and store it in the
proper format.
When the builder is created, this source ®le is stored as part of the builder in the TeamConnection database; during a build, the build server creates and runs a local version of this ®le. Specify the name you want for this local ®le in theScript ®eld. For example, you might specify these values:
± File type - text
± Script - c_compile.cmd
± Source ®le - c:\src\c_compile.cmd
When this builder is created, the contents of c:\src\c_compile.cmd are stored in the builder. When this builder is invoked, TeamConnection creates a ®le named c_compile.cmd, writes the build script into this ®le, and then runs it.
v If the builder is being used to only collect a set of build objects (for example, the ALL: rule in make®les), specify these values:
± File type - none
± Script - null
This prevents the build process from extracting input and output parts. See ªSynchronizing the build of unrelated partsº on page 196 for an example.
Environment
This is the name of the environment supported by the builder, such as OS/2, Windows, AIX,
Chapter 12. Working with build scripts and builders 149
