30.1.1 Understanding how templates are organized
Your Mif2Go distribution includes the collections of configuration templates listed in Table B-1. These templates are linked together by references that extend through the chains, from your project configuration file through templates in %OMSYSHOME%\m2g subdirectories, to the very end of the configuration chain at %OMSYSHOME%\common\system\config\omsys.ini. See §30.1.3 Understanding how templates are chained together
Configuration templates include the following groups:
General configuration settings, located in config directories
Macro definitions, located in macros directories
Each template in a system subdirectory is paired with an editable configuration file in the corresponding local subdirectory. The system member of each pair contains default settings. The local member of each pair starts out empty; you add settings to override the default settings referenced in the system member. Your configuration files always reference the local member. The local member references its system counterpart, which in turn references the local member of the next template up the chain.
General configuration settings
The settings in general configuration templates establish default values for features that are not likely to differ from one project to the next, or from one output type to the next. General configuration templates are located in the following directories:
%OMSYSHOME%\m2g\system\config: default general configuration settings
%OMSYSHOME%\m2g\local\config: your overrides to the system settings
General-purpose macros are defined in macro library templates. Each configuration section in these templates is the name of the macro being defined. Macro library templates are located in the following directories:
%OMSYSHOME%\m2g\system\macros: definitions of general-purpose macros
%OMSYSHOME%\m2g\local\macros: definitions of your own macros
> 30 Working with templates > 30.1 Working with configuration templates > 30.1.1 Understanding how templates are organized