IBM SC34-4499-03 manual Modifying the contents of a build script, Putting a builder to work

Chapter 12. Working with build scripts and builders

GUI: From the Actions menu of the TeamConnection Tasks Window, select Parts → Modify → Properties. On the Modify Part Properties window, type the name of the builder in the Builder ®eld.

DEBUG parameters, and then runs the command ®le against a local copy of hello.c. If the test is successful, the script correctly builds hello.obj in the current directory, and DEBUG is interpreted correctly.

Modifying the contents of a build script

Sometimes you need to modify the contents of a build script. Remember that a build script is stored as part of the builder itself. Because builders are not versioned, you do not check them out as you would most TeamConnection parts. Instead, follow these steps:

1.Extract the builder (in which the build script is stored) from the TeamConnection database.

2.Make your changes at your workstation.

3.Store the contents back into the TeamConnection database by using the builder -modify command.

For example, to modify the build script in ªWriting an executable ®le for a build scriptº on page 153, you ®rst issue the following command:

teamc builder -extract c_builder2 -to d:\build\c_builder2

Then, you use an editor to update d:\build\c_builder2. To move the updated build script back into TeamConnection, you issue the following command:

teamc builder -modify c_builder2 -from d:\build\c_builder2

The builder is an implied dependency for any part that uses it. Therefore, the next time you build the application that uses the modi®ed builder, all the parts that use it get rebuilt.

Putting a builder to work

For an application to use a builder, the builder must be attached to the TeamConnection parts that it will build.

For an existing part, do one of the following: v

155