|
599
|
1 |
GT 0063 Emulation Enhancements
|
|
|
2 |
|
|
|
3 |
1. EPOCROOT check in E32env.PM
|
|
|
4 |
|
|
|
5 |
Changed from static data to an active BEGIN{} section which tests the EPOCROOT
|
|
|
6 |
environment variable and constructs the rest of the E32env::Data hash accordingly.
|
|
|
7 |
|
|
|
8 |
EPOCROOT checking is:
|
|
|
9 |
|
|
|
10 |
- environment variable must exist
|
|
|
11 |
- EPOCROOT must begin with \
|
|
|
12 |
- EPOCROOT must specify an existing directory
|
|
|
13 |
|
|
|
14 |
Most clients are expected to use $E32Env::Data{EPOCPath} as the raw "epoc32" directory.
|
|
|
15 |
|
|
|
16 |
|
|
|
17 |
2. Path_MakeEAbs in PATHUTL.PM
|
|
|
18 |
|
|
|
19 |
Variant of Path_MakeAbs.
|
|
|
20 |
Path_MakeEAbs takes (EPOCPath, BasePath, ...) and makes the list of directories into
|
|
|
21 |
absolute paths relative to BasePath. The extra functionality is that paths beginning
|
|
|
22 |
|
|
|
23 |
+\...
|
|
|
24 |
|
|
|
25 |
are treated as paths relative to EPOCPath rather than BasePath.
|
|
|
26 |
|
|
|
27 |
As a regression change, this change also extends to paths which begin \epoc32\, which
|
|
|
28 |
copes with the large number of existing absolute \epoc32 paths (e.g. SYSTEMINCLUDE
|
|
|
29 |
statements in MMP files).
|
|
|
30 |
|
|
|
31 |
Path_MakeEAbs is used in MMP.PM to handle SYSTEMINCLUDE, DEFFILE and USERINCLUDE
|
|
|
32 |
statements, and in BLDMAKE.PL to handle PRJ_EXPORTS and PRJ_TESTEXPORTS.
|