Entering content frame

 Comparison Between MAXDB VMAKE and a Conventional Make Program 

To those who are familiar with the traditional UNIX make or Microsoft nmake programs, some of the features of VMAKE might seem a little surprising.

·        Since all of the include files are copied to sys/wrk/incl and all of the source files are copied to a temporary directory before translation, file names in the error messages output by the compiler never point to the actual source file.

·        The program always attempts to generate as much as possible, and does not stop after the first error. This is equivalent to the -k option in make.

·        Each object file has a date file (for example, sys/wrk/fast/dates/SAPDB/HelloWorld.c.dat). An new object file is created:

·         If the existing object file is older than the source file (as in make)

·         If the timestamp of the date file differs from that of the source file.

 

Leaving content frame