All tools may store some global data into the file MCUTOOLS.INI. The tool first search for this file in the directory of the tool itself (path of the executable). If there is no MCUTOOLS.INI file in this directory, the tool looks for a MCUTOOLS.INI file located in the MS Windows installation directory (e.g. C:\WINDOWS).
Example
C:\WINDOWS\MCUTOOLS.INI D:\INSTALL\PROG\MCUTOOLS.INI
If a tool is started in the D:\INSTALL\PROG\DIRECTOY, the initialization file in the same directory than the tool is used (D:\INSTALL\PROG\MCUTOOLS.INI).
But if the tool is started outside the D:\INSTALL\PROG directory, the initializa-tion file in the Windows directory is used (C:\WINDOWS\MCUTOOLS.INI).
The following section gives a short description of the entries in the MCU-TOOLS.INI file:
Freescale Semiconductors, Inc.
[Installation] Section
Entry: Path
Arguments: Last installation path.
Description Whenever a tool is installed, the installation script stores the installation destination directory into this variable.
Example Path=c:\install
Entry: Group
Arguments: Last installation program group.
Description Whenever a tool is installed, the installation script stores the installation program group created into this variable.
Example Group=Assembler
[Options] Section
Entry: DefaultDir
Arguments: Default Directory to be used.
Description Specifies the current directory for all tools on a global level (see also environment variable DEFAULTDIR).
Example DefaultDir=c:\install\project
[XXX_Assembler] Section
instead of XXX, the actual backend name appears
Entry: SaveOnExit
Arguments: 1/0
Description 1 if the configuration should be stored when the assembler is closed, 0 if it should not be stored. The assembler does not ask to store a configuration in either cases.
Entry: SaveAppearance
Freescale Semiconductors, Inc.
Arguments: 1/0
Description 1 if the visible topics should be stored when writing a project file, 0 if not. The command line, its history, the windows position and other topics belong to this entry.
This entry corresponds to the state of the check box ‘Appearance’
in the ‘Save Configuration’ dialog box.
Entry: SaveEditor
Arguments: 1/0
Description 1 if the editor settings should be stored when writing a project file, 0 if not. The editor setting contain all information of the editor configuration dialog box.
This entry corresponds to the state of the check box ‘Editor Con-figuration’ in the ‘Save ConCon-figuration’ dialog box.
Entry: SaveOptions
Arguments: 1/0
Description 1 if the options should be contained when writing a project file, 0 if not.
This entry corresponds to the state of the check box ‘Options’ in the ‘Save Configuration’ dialog box.
Entry: RecentProject0, RecentProject1, ...
Arguments: names of the last and prior project files
Description This list is updated when a project is loaded or saved. Its current content is shown in the file menu.
Example SaveOnExit=1
[Editor] Section
Entry: Editor_Name
Arguments: The name of the global editor
Description Specifies the name of the editor used as global editor. This entry has only a description effect. Its content is not used to start the editor.
Saved: Only with ‘Editor Configuration’ set in the File->Configuration Save Configuration dialog box.
Entry: Editor_Exe
Arguments: The name of the executable file of the global editor (including path).
Description Specifies the file name which is started to edit a text file, when the global editor setting is active.
Saved: Only with ‘Editor Configuration’ set in the File->Configuration Save Configuration dialog box.
Entry: Editor_Opts
Arguments: The options to use with the global editor
Description Specifies options (arguments), which should be used when start-ing the global editor. If this entry is not present or empty, “%f” is used. The command line to launch the editor is build by taking the Editor_Exe content, then appending a space followed by the con-tent of this entry.
Saved: Only with ‘Editor Configuration’ set in the File->Configuration Save Configuration dialog box.
Example [Editor]
editor_name=IDF
editor_exe=C:\metrowerks\prog\idf.exe editor_opts=%f -g%l,%c
Freescale Semiconductors, Inc.
Example
The following example shows a typical layout of the MCUTOOLS.INI:
[Installation]
The assembler does not change the default.env file in any way. The assembler only reads the contents. All the configuration properties are stored in the configuration file. The same configuration file can and is intended to be used by different applica-tions (assembler, Linker, etc.).
The processor name is encoded into the section name, so that Assembler for differ-ent processors can use the same file without any overlapping. Differdiffer-ent versions of the same Assembler are using the same entries. This mainly plays a role when options only available in one version should be stored in the configuration file. In such situations, two files must be maintained for the different Assembler versions.
If no incompatible options are enabled when the file is last saved, the same file can be used for both Assembler version.
The current directory is always the directory, where the configuration is in. If a con-figuration file in a different directory is loaded, then the current directory also changes. When the current directory changes, also the whole default.env file is reloaded. Always when a configuration file is loaded or stored, the options in the environment variable ASMOPTIONS is reloaded and added to the project options.
This behavior has to be noticed when in different directories different default.env