Where more than one SDK is installed on the same drive, the
EPOCROOT
environment variable must be set to the location in which
one of the emulators has been installed. This emulator then becomes the target
for the build process (the "active emulator") and can be launched by invoking
epoc.bat
.
To set EPOCROOT
as a user or system variable on Windows
NT:
From the start menu follow Settings->Control
Panel->System->Environment
.
In the Variable box type EPOCROOT
and in the Value
box the directory to be pointed to. The EPOCROOT
setting must not
contain a drive letter and the target directory must exist. All new command
prompts will have the variable set from then on.
On Windows 98, EPOCROOT
can be set in the
autoexec.bat
file.
For example h:\sdk1\vX\epoc32
and
h:\sdk2\vX\epoc32
would be set to
\sdk1\vX\
or \sdk2\vX\
.
Alternatively EPOCROOT
may be set from the command line
or batch file. The process is:
Open a command prompt (MS DOS box) or batch file.
Specify the following instruction:
set epocroot=\directory\another\
This will only last for as long as the command prompt.
For example, the EPOCROOT
variable for
h:\sdk1\vX\epoc32
and h:\sdk2\vX\epoc32
would be set using:
set epocroot=\sdk1\vX\
set epocroot=\sdk2\vX\
SDKs and emulators must be installed to one drive.
If the environment variable is set to a \ then the SDK will work in the same way as releases prior to v6.0, with epoc32 being in the root.
If the EPOCROOT
environment variable is missing or
points to an invalid location, the build tools will report this as an error and
then terminate.