Download TASKING VX-toolset for C166 User Guide

Using the Utilities
The macro FOOD is expanded as meat and/or vegetables and water at the moment it is used in
the export line, and the environment variable FOOD is set accordingly.
Predefined macros
Macro
Description
MAKE
Holds the value mk166. Any line which uses MAKE, temporarily overrides the option
-n (Show commands without executing), just for the duration of the one line. This way
you can test nested calls to MAKE with the option -n.
MAKEFLAGS
Holds the set of options provided to mk166 (except for the options -f and -d). If this
macro is exported to set the environment variable MAKEFLAGS, the set of options is
processed before any command line options. You can pass this macro explicitly to
nested mk166's, but it is also available to these invocations as an environment variable.
PRODDIR
Holds the name of the directory where mk166 is installed. You can use this macro to
refer to files belonging to the product, for example a library source file.
DOPRINT = $(PRODDIR)/lib/src/_doprint.c
When mk166 is installed in the directory c:/Tasking/bin this line expands to:
DOPRINT = c:/Tasking/lib/src/_doprint.c
SHELLCMD
Holds the default list of commands which are local to the SHELL. If a rule is an
invocation of one of these commands, a SHELL is automatically spawned to handle
it.
$
This macro translates to a dollar sign.Thus you can use "$$" in the makefile to represent
a single "$".
Dynamically maintained macros
There are several dynamically maintained macros that are useful as abbreviations within rules. It is best
not to define them explicitly.
Macro
Description
$*
The basename of the current target.
$<
The name of the current dependency file.
$@
The name of the current target.
$?
The names of dependents which are younger than the target.
$!
The names of all dependents.
The $< and $* macros are normally used for implicit rules. They may be unreliable when used within
explicit target command lines. All macros may be suffixed with F to specify the Filename components
(e.g. ${*F}, ${@F}). Likewise, the macros $*, $< and $@ may be suffixed by D to specify the Directory
component.
The result of the $* macro is always without double quotes ("), regardless of the original target having
double quotes (") around it or not.
253