Open Watcom Developer's Guide - HEAnet Mirror Service

Building
5.2 Pmake
Many of the projects use the "pmake" features of builder (see builder.doc ) or standalone
pmake tool. If you want to see its guts, the pmake source is in bld\pmake.
Each makefile has a comment line at the top of the file which is read by pmake. Most of our
lang.ctl files will have a line similar to this:
pmake -d build -h ...
this will cause wmake to be run in every subdirectory where the makefile contains "build"
on the #pmake line. See for instance the C compiler makefiles (in bld\cc) for an example.
You can also specify more parmeters to build a smaller subset of files. This is especially
useful if you do not have all required tools/headers/libraries for all target platforms.
For example:
builder rel2 os_nt
will (generally) build only the NT version of the tools.
A word of warning: running a full build may take upwards of two hours on a 1GHz machine.
There is a LOT to build! This is not your ol’ OS kernel or a single-host, single-target C/C++
compiler.
It is generally possible to build specific binaries/libraries by going to their directory and
running wmake. For instance to build the OS/2 version of wlink you can go to bld\wl\os2386
and run wmake there (note that the process won’t successfully finish unless several required
libraries had been built). Builder is useful for making full "release" builds while running
wmake in the right spot is the thing to do during development.
Happy Building!
28 Pmake