Freescale Semiconductor Microcontrollers Local Co nfigur ation File

Debugger Engine Environment Variables
Local Configuration File (usually project.ini)
844 Microcontrollers Debugger Manual
Local Configuration File (usually project.ini)
The Debugger does not change the default.env file. Its content is read only. All
configuration properties are stored in the configuration file. The same configuration file
can be used by different applications.
The shell uses the configuration file with the name project.ini in the current
directory only. That is why this name is also suggested to be used with the Debugger. Only
when the shell uses the same file as the compiler, the editor configuration written and
maintained by the shell can be used by the Debugger. Apart from this, the Debugger can
use any file name for the project file. The configuration file has the same format as
windows .ini files. The Debugger stores its own entries with the same section name as
in the global mcutools.ini file.
The current directory is always the directory containing the configuration file. If a
configuration file in a different directory is loaded, then the current directory also changes.
When the current directory changes, the default.env file is reloaded. Always when a
configuration file is loaded or stored, options in the environment variable
COMPOPTIONS are reloaded and added to the project options. Beware of this behavior
when a different default.env file exists in different directories, which contain
incompatible options in COMPOPTIONS.
When a project is loaded using the first default.env, its COMPOPTIONS are added
to the configuration file. If this configuration is stored in a different directory, where a
default.env file exists with incompatible options, the Debugger adds options and
marks the inconsistency. Then a message box appears to inform the user that the
default.env options were not added. In such a situation the user can either remove the
option from the configuration file with the option settings dialog box or remove the option
from default.env with the shell or a text editor, depending on which options are
needed in the future.
At startup there are three ways to load a configuration:
• use the command line option prod
•the project.ini file in the current directory
• or Open Project entry from the file menu.
If the option prod is used, then the current directory is the directory in which the project
file is located. If prod is used with a directory, the project.ini file in this directory is
loaded.