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