Freescale Semiconductor Microcontrollers - Manual (Page 842)

Debugger Engine Environment Variables
Debugger Environment
842 Microcontrollers Debugger Manual
Debugger Environment
Various parameters of the Debugger may be set using environment variables. The syntax
is always the same:
Parameter = KeyName "=" ParamDef.
NOTE Do not use blanks in the definition of an environment variable.
For example:
GENPATH=C:\INSTALL\LIB;D:\PROJECTS\TESTS;/usr/local/lib;/
home/me/my_project
The Debugger parameters may be defined in several ways:
• Using system environment variables supported by your operating system.
• Putting the definitions in a file called DEFAULT.ENV in the default directory.
NOTE The maximum length of environment variable entries in the DEFAULT.ENV/
.hidefaults
is 4096 characters.
• Putting definitions in a file given by the value of the system environment variable
ENVIRONMENT.
NOTE The default directory mentioned above can be set by using the system
environment variable
DEFAULTDIR: Default Current Directory .
When looking for an environment variable, all programs first search the system
environment, then the DEFAULT.ENV file and finally the global environment file given
by ENVIRONMENT. If no definition can be found, a default value is assumed.
NOTE Ensure that no spaces exist at the end of environment variables.
The Current Directory
The most important environment for all tools is the current directory. The current
directory is the base search directory where the tool begins to search for files (for example,
the DEFAULT.ENV/.hidefaults file)
Normally, the current directory of a tool is determined by the operating system or program
that launches another one (for example, WinEdit).
For MS Windows-based operating systems, the current directory definition is more
complex.