Open Watcom Developer's Guide - HEAnet Mirror Service

Building
3.2 Project Names
Each project must be given a unique name, which should also be a valid directory name under
FAT file systems (8.3 convention).
3.3 Makefiles
Each makefile should be located in the object file directory - ie. no more of this silly cd’ing
into the object directory based on crystal-balls and what not. The makefile must define the
following:
host_os:
host_cpu:
os which the resulting executable code will run on
architecture which the resulting executable code will run on.
proj_name: the project name
Valid values for host_cpu are 386, i86, axp, ppc. These should be self-explanatory. Valid
values for host_os are dos, nt, os2, nov, qnx, win, osi, linux. These should be
self-explanatory for the most part, with one possible exception: osi stands for OS
Independent, the executables can run on multiple OSes if appropriate loader stub is provided.
The makefile must then include cproj.mif. This will define all sorts of make variables, which
can then be used to build the project. A list of the most important of these variables and what
they can be used for is included below.
A makefile should also include deftarg.mif, for definition of the required clean target, and
defrule.mif, which has the default build rules for C, C++ and assembly sources. A makefile is
free to override these defaults as long as it follows the following conventions:
1. Tools which have macros defined for them must be referred to by the macros -
these are currently (any additions should be brought to my attention):
$(CC):
$(CPP):
The C compiler
The C++ compiler
$(LINKER): The linker
$(LIBRARIAN): The librarian
16 Makefiles