1.4 Auditing 16-bit Tools

Compilers, linkers, and other tools written to run on MS-DOS or Windows (16-bit tools) require special handling when used in audited builds with omake.

The program vdmaudit allows auditing of 16-bit tools. To use vdmaudit, you need to have omake run vdmaudit and let it call the 16-bit tool. This involves either editing the makefile where it calls the 16-bit tool, or if your makefile defines a macro for each 16-bit tool, redefining the macros in the makefile or on the omake command line.

If the makefile defines a macro for each 16-bit tool, you can change the macros to call vdmaudit. For example, if your makefile contains macros like

CPP=cl.exe
LINK=link.exe

change them as follows:

CPP=vdmaudit cl.exe
LINK=vdmaudit link.exe

You can redefine the macros on the omake command line like this:

omake -EN -f disptree.mak CPP="vdmaudit cl.exe" LINK="vdmaudit link.exe"

Call all 16-bit tools from vdmaudit; if you do not, omake does not audit all tools and the configuration record is incomplete.

An alternative method for auditing 16-bit tools is to use the ClearCase Virtual Device Driver (VDD). To install the VDD during ClearCase installation, select 16-bit build auditing on the ClearCase Client Options or ClearCase Server Options page. The VDD runs any time a 16-bit tool is run, whether during an audit or not. However, the VDD can cause 16-bit tools to fail to display all output or to fail to clear the screen when done.