Entering content frame

 Process Flow of the MAKE Operation 

At the beginning of a MAKE operation, VMAKE uses the date files to determine the targets that have to be recreated. The system then searches for all of the relevant module files in the hierarchy (1) and copies them to the temporary working directory tmp (General Directory Structure) (2).

The files are then further processed in this directory with VMAKE tools. These tools are essentially Perl scripts (3). VMAKE selects the appropriate Perl scripts on the basis of the programming language in the module files (Selecting the Translation Tools). The Perl scripts are platform specific, and call the respective compilers, translators, and unpackers.

The output files produced as a result (object files and include files) are initially also stored in the temporary working directory (4). VMAKE then copies the object files to the respective obj directory and the include files to the incl-directory for the relevant layer (5).

If VMAKE is operating in debug mode, the module files are also copied to the corresponding debug directory.

A date file is stored for every module file that is used to create a target.

The relevant tools also perform the link operations the temporary directory, based on the applicable link descriptions. The output files are also stored here. Following this, VMAKE copies the targets in the relevant directories (6).

The files located in the temporary working directory are deleted once the targets have been successfully created. If an error occurs while the targets are being created, the files are not deleted from the temporary directory.

VMAKE also logs the entire software creation process.

Defining the MAKE Operation

VMAKE Logs

Translation Process

Link Operation

 

Leaving content frame