It is possible to use macros in your environment settings, as the following listing displays.
MyVAR=C:\test TEXTPATH=$(MyVAR)\txt OBJPATH=${MyVAR}\obj
In the above listed example, TEXTPATH is expanded to ` C:\test\txt', and OBJPATH is expanded to ` C:\test\obj'.
From the example above, you can see that you either can use $ () or $ {}. However, the variable referenced has to be defined somewhere.
In addition, the following special variables in Listing: Usual locations for the mcutools.ini files are allowed. Note that they are case-sensitive and always surrounded by {}. Also the variable content contains a directory separator ` \' as well.
{Compiler}
This is the path of the directory one level higher than the directory for executable tool. That is, if the executable is C:\Freescale\prog\linker.exe, then the variable is C:\Freescale\. Note that {Compiler} is also used for the Assembler.
{Project}
Path of the directory containing the current project file. For example, if the current project file is C:\demo\project.ini, the variable contains C:\demo\.
{System}
This is the path where Windows OS is installed, e.g., C:\WINNT\.