Using MKS Make

Controlling MKS Make
Special Macros
Control Macros
Target Directive Description
.SOURCE.x When trying to locate a file with a name ending in the suffix
.x, search first in the list of directories defined by the
associated prerequisite list. The following example directs
make to look in two different sets of directories for source
and object file targets.
.SOURCE$O : $HOME/proj/object /rd/
object
.SOURCE.c : $HOME/proj/src /rd/src
.SUFFIXES When inferring a rule using suffix rules, the list of valid
suffixes is defined by this target’s associated prerequisite list.
If you specify the special target more than once, MKS Make
adds each list of suffixes to a single list, in the order they
appear. The following example specifies four valid suffixes
for use with suffix rules.
.SUFFIXES : y .c $O $E
To clear the list, specify this special target with an empty
prerequisite list. The .SUFFIXES special target has no
effect on metarule inferencing.
For additional information, see “Suffix Rules” on page 50.
Special macros usually behave like macros, except they can hold special
kinds of information. MKS Make supports two kinds of special macros;
control macros and runtime macros.
Control macros control MKS Make’s behavior. A control macro having the
same function as an attribute, also has the same name.
MKS Make defines the runtime macros during the process of making targets.
Runtime macros usually only serve a useful purpose within recipes; they can
expand to contain the name of prerequisites or targets within recipes.
Dynamic prerequisite macros (a special type of runtime macro), however,
serve a useful function when used in prerequisite lists; they can refer to the
associated target’s name (in full, or in part).
MKS Make groups control macros into two sets: string-valued macros and
attribute macros.
MKS Make automatically creates internally defined macros. For example,
you can use $(PWD) to expand to the name of the present working directory.
34 MKS Toolkit