The Source Integrity Professional Edition User Guide - MKS

Building Projects With Source Integrity
Templates and
Configuration
Language
Templates and
Variable
Expansion
4. You could also add those included files as members of the project
with the pj finddep command:
c:\usr\work\hello.c depends on:
c:\wcc\include\fin_func.h
Add ‘c:\wcc\include\fin_func.h’ to project?
[ynq](y):
To add the file, press .
This procedure only needs to be done once for each project, although
the makefile will have to be updated (with pj mkmf) if new members
are added to the project. You should also
add the makefile as a member of the project
put the makefile under revision control
To build the project, simply give the command pj build.
If SYSTEM is defined in the environment as “nt”
@@
@set OS=$getenv(SYSTEM)
@OS@
TEXT@OS@TEXT
Line one expands to a literal @ character.
Line two sets a variable named OS to “nt” but does not produce
any output in the makefile.
Line three produces a line in the expanded makefile containing
the value of the variable OS (in this example, “nt”).
Line four produces a line in the makefile containing the text
TEXTntTEXT
If a template named base.t contains the following lines
@set version=1
@set system=$getenv(SYSTEM)
# Generated @SYSTEM@ makefile, Version @version@
OBJ=@Objects@
target.exe: $(OBJ)
bcc -o $@@ $(OBJ)
@Depends
and the environment variable SYSTEM is set to “nt”, running the
command
pj mkmf -T base.t -M makefile
240 Source Integrity Professional Edition