The bottom hierarchy of a VMake project is built by modules. A module definition is constructed by a set of appropriate rules which determine the dependences of all files and objects in a particular directory. For each module or rather within each directory a module description file vmfile.mk must exist which holds the module definition rules. For a certain run of VMake all module definitions are processed and the required dependence information is extracted. This information is examined using the already existing information of project dependences from the project save file. The combined information is saved again for later runs. Thus, the local module information is integrated into the global project information structure and consistently administrated. This global information structure reduces the overhead of handling obsolete files and objects significantly. Furthermore, any modification of rule definitions is automatically detected and processed.
Module-Directory
This rule defines a symbolicName for the module directory or rather it is
simply the name of the module. This must be the first rule of each module
description file.
