IBM SC34-4499-03 manual Creating a rules le, Le mask, Connect, Content

used in the commands is mywork. After the commands are issued, the resulting build tree is shown using the TeamConnection GUI.

Creating a rules ®le

The import rules ®le is a text ®le that describes how you want TeamConnection to create and connect parts. In this ®le you supply a set of rules, one per line, using the following syntax:

®le mask

The mask specifying the names of the ®les to which this rule applies. The * and ? wildcards are supported. For example, you could specify ®le names such as *.cbl, abc*.cpp, or foo\src\*.obj.

type The type of contents of the ®les to which the rule applies when they are stored in TeamConnection as a part. Allowed values are binary, text, none, or ignore.

If you specify ignore as the ®le type, then all ®les that match the ®le mask are bypassed.

builder The name of the TeamConnection builder to be associated with the part. The

builder is not created for you. If you specify a builder, it must exist in TeamConnection before you run fhomigmk. A value of none means that no builder will be associated with the part.

parser The name of the TeamConnection parser to be associated with the part. The

parser is not created for you. If you specify a parser, it must exist in TeamConnection before you run fhomigmk. A value of none means that no parser will be associated with the part.

connect

How the part will be connected to other parts in TeamConnection. The following values are allowed:

vinput

voutput

vdependent

vnone

When none is speci®ed, the part is not connected to another part even though

a dependency was found for the part in the make ®le. For example, when you indicate none for a ®le mask of *.h ®les, the *.h ®les are created in

TeamConnection, but not connected to the ®les that include them. The value you will use most often is input.

content

Where the initial content of the part can be found:

vnone indicates that the part is initially created as empty.

vdirectory\ indicates to concatenate with the name of the ®le in the make®le. This is where the contents are expected to be found.

Appendix B. Importing make®le information into TeamConnection 237