Filter
Top Products
Debugger Engine Environment Variables
Local Configuration File (usually project.ini)
848
Microcontrollers Debugger Manual
Select HI-WAVE section to retrieve value from:
• if an entry Windows0 or Target can be retrieved from section [HI-WAVE] then:
use [HI-WAVE]
• else if an entry Windows0 or Target can be retrieved from section [DEFAULTS]
then:
use [DEFAULTS]
•else:
use [HI-WAVE]
The environment variables are loaded from the default.env file:
• If an entry Layout=lll exists, the layout file lll.hwl is loaded and executed.
• The target is set (if entry Target=ttt exists load target ttt).
• If an entry Project=ppp exists, the command file ppp is executed.
• The configuration file (*.hwc) is loaded (entry configuration=*.hwc).
Environment Variable Paths
Most environment variables contain path lists indicating where to search for files. A path
list is a list of directory names separated by semicolons following the syntax below:
PathList = DirSpec {";" DirSpec}.
DirSpec = ["*"] DirectoryName.
Example:
GENPATH=C:\INSTALL\LIB;D:\PROJECTS\TESTS;/usr/local/hiwave/
lib;/home/me/my_project
If a directory name is preceded by an asterisk ("*"), the programs recursively search the
directory tree for a file, not just the given directory. Directories are searched in the order
they appear in the path list.
Example:
GENPATH=.\;*S;O
NOTE Some DOS environment variables (like GENPATH, LIBPATH, etc.) are used.
We strongly recommend working with WinEdit and setting the environment by means of a
DEFAULT.ENV file in your project directory. This project directory can be set in
WinEdit's Project Configure menu command. This way, you can have different projects in
different directories, each with its own environment.