z/TPF Program Management - IBM

Makefiles
Control files
4 z/TPF Program Management
Makefiles are used by the maketpf command to specify the program name, type,
component, and any special build options that are required for a clean build
(assemble, compile, and link). All information is coded by assignment statements
and adheres to GNU make syntax.
Makefiles refer to environment files to define the paths for files that you need for the
build process and to specify the directories to use for output. Makefiles also include
maketpf.rules as their last statement to include the compile, assemble, and link
rules for z/TPF processing.
The maketpf.rules file includes a set of common rules files that are located in the
tpftools/include_ztpf and tpftools/include_ztpf_user directories. The audits in
these files are run by maketpf to check build input and output, and can issue errors
and warning messages. These audits can be external programs that check for
errors. For example, the maketpf audit that checks for programs that export data
objects needing relocation is defined in these files. See “Resolve TSOC0001W
warnings” on page 70 for more information about this maketpf audit.
You can add and audit rules in the maketpf.rules_setup1 and
maketpf.rules_setup2 files. If you want to change a rules file that was included by
IBM ® , move the appropriate file to the tpftools/include_ztpf_user directory (this
directory is searched before the tpftools/include_ztpf directory) and modify the
file.
See “Assemble, compile, and link (build) application programs” on page 57 for tasks
dealing with makefiles. For reference information about coding makefiles, enter man
maketpf.mak on your Linux build system.
Control files contain a list of programs that can be built by the MakeTPF build
solution. Control files do the following:
v Define program build options such as makefile, build order, whether the program
is offline or online, and others
v Are used as input for bldtpf to create general file loader, image loader, and
E-type loader input files
v Are used as input for bldtpf to create the program attribute table (PAT)
v Define program attributes (such as protection, restricted use, and so on)
v Are used for system programs (tpf.cntl) and user applications (usr.cntl).
The MakeTPF build solution recognizes two system-level control files: tpf.cntl and
usr.cntl. However, you can arrange control files into smaller and more
manageable chunks by using include statements in the control files. See Table 4 on
page 103 for information about the set of control files that are included.
You can also use control files on a project level. See “Assemble, compile, and link
(build) application programs” on page 57 for tasks showing how this can be done.
For reference information about control files and the control file format, see “Control
files” on page 103 and the prolog of base/cntl/tpf.cntl.