Local Configuration File

The configuration file stores all configuration properties. Different applications use the same configuration file.

The shell uses the project.ini configuration file in the current directory. When the shell uses the same file as the compiler, the shell writes and maintains the Editor Configuration used by the compiler. Apart from this, the compiler can use any filename for the project file. The configuration file has the same format as the windows *.ini files. The compiler stores its own entries with the same section name as those in the global mcutools.ini file. The compiler backend is encoded into the section name, so that a different compiler backend can use the same file without any overlapping. Different versions of the same compiler use the same entries. When you must store options available in only one compiler version in the configuration file, you must maintain a separate configuration file for each different compiler version. If no incompatible options are enabled, you may use the same file for both compiler versions.

Be aware of these rules when changing the directory or making changes to the configuration file:

• The current directory is always the directory in which the configuration file is located.
• Loading a configuration file in a different directory changes the current directory.
• Changing the current directory reloads the entire default.env file.
• Loading or storing a configuration file reloads the options in the environment variable COMPOPTIONS and adds the options to the project options. This becomes an issue when different default.env files, containing incompatible options in the COMPOPTIONS variable, exist in different directories.
• Loading a project using the default.env adds the options in COMPOPTIONS to the configuration file.
  • Storing this configuration in a different directory which contains a default.env with incompatible options adds the options to default.env. The compiler remarks the inconsistency.
  • Use the option settings dialog box to remove the option from the configuration file, or remove the option from the default.env with the shell or a text editor.

At startup, use one of two methods to load a configuration:

• Use the -Prod: Specify Project File at Startup command line option
• Use the project.ini file in the current directory.

Using the -Prod option uses the directory which contains the project file as the current directory. Specifying the directory when using the -Prod option loads the project.ini file in this directory.

Local Configuration File Entries documents the sections and entries you can include in a project.ini file.