The Source Integrity Professional Edition User Guide - MKS

Managing Projects and Sandboxes
For more information about
the -v option, see the online
reference for the pj command.
where var is the name of an attribute, value is the value it is set to, and
file is one or more project members the attribute will be assigned to. If
file is omitted, the attribute is assigned to all project members.
Example
You might use attributes to identify the components needed to build
the NT and OS/2 versions of the gamble project.
You could accomplish this by creating an attribute named “SYS” for
all project members and assigning appropriate values for individual
members.
Files that are used to build both versions of the command (for
example, header and most code files) are assigned a value of
“Both”.
Files used only for the NT version are assigned a value of “NT”.
Files used only for the OS/2 version are assigned a value of
“OS2”.
The easiest way to implement this for the gamble project is as follows:
1. Use the pj addrule command to assign the SYS attribute to all
project members, with a value of “Both”.
pj addrule SYS=Both
2. Run the command twice more to change the value of SYS for
those members used for only one operating system
pj addrule SYS=NT nt\filesys.c
pj addrule SYS=OS2 os2\filesys.c
Note To change a member attribute, simply run pj addrule again and
assign a new value.
With these attributes in place, you can use the -v option to the project
commands to specify that they should operate only on members with
a particular attribute, or an attribute set to a certain value.
For example, to print information about all project members with the
SYS attribute, enter
pj print -v SYS
To see the same information about only those members associated
with the NT platform, you would enter
pj print -v SYS=NT
154 Source Integrity Professional Edition