|
28
|
1 |
The pre-included header file used in builds (.hrh) is normally defined
|
|
|
2 |
inside a text file located at $(EPOCROOT)/epoc32/tools/variant/variant.cfg
|
|
|
3 |
in each kit.
|
|
|
4 |
|
|
|
5 |
This is an unnecessary extra file to maintain if you already define all the
|
|
|
6 |
other kit properties in an XML file in the $(EPOCROOT)/epoc32/sbs_config
|
|
|
7 |
folder.
|
|
|
8 |
|
|
|
9 |
This change allows kit owners to define the .hrh file name in the XML instead
|
|
|
10 |
of using an additional variant.cfg file.
|
|
|
11 |
|
|
|
12 |
An example of this is shown in $(SBS_HOME)/examples/os_properties.xml
|
|
|
13 |
where the VARIANT_HRH parameter is set as follows,
|
|
|
14 |
|
|
|
15 |
<set name='VARIANT_HRH' value='$(EPOCINCLUDE)/feature_settings.hrh'/>
|
|
|
16 |
|
|
|
17 |
|
|
|
18 |
In the unusual case where you want to build without a .hrh file at all (maybe
|
|
|
19 |
to create an epoc32 tree from scratch) there is a variant "nohrh" which
|
|
|
20 |
simply sets VARIANT_HRH as above to an empty file. Example usage would be,
|
|
|
21 |
|
|
|
22 |
sbs -b bootstrap/bld.inf -c tools2.nohrh
|
|
|
23 |
|
|
|
24 |
Note that, in general, actual code will not build properly without a .hrh
|
|
|
25 |
file to configure it.
|