|
70
|
1 |
; hscontentcontrolexample.pkg
|
|
|
2 |
; This is an auto-generated PKG file by Carbide.
|
|
|
3 |
; This file uses variables specific to Carbide builds that will not work
|
|
|
4 |
; on command-line builds. If you want to use this generated PKG file from the
|
|
|
5 |
; command-line tools you will need to modify the variables with the appropriate
|
|
|
6 |
; values: $(EPOCROOT), $(PLATFORM), $(TARGET)
|
|
|
7 |
; Also, the resource file entries should be changed to match the language
|
|
|
8 |
; used in the build. For example, if building for LANGUAGE_01, change the file
|
|
|
9 |
; extensions .rsc to .r01.
|
|
|
10 |
;
|
|
|
11 |
;Language - standard language definitions
|
|
|
12 |
&EN
|
|
|
13 |
|
|
|
14 |
; standard SIS file header
|
|
|
15 |
#{"HS ContentControl"},(0xE88D7143),1,0,0
|
|
|
16 |
|
|
|
17 |
;Localised Vendor name
|
|
|
18 |
%{"Vendor-EN"}
|
|
|
19 |
|
|
|
20 |
;Unique Vendor name
|
|
|
21 |
:"Vendor"
|
|
|
22 |
|
|
|
23 |
;Supports Series 60 v 3.0
|
|
|
24 |
[0x101F7961], 0, 0, 0, {"Series60ProductID"}
|
|
|
25 |
|
|
|
26 |
;Files to install
|
|
|
27 |
;You should change the source paths to match that of your environment
|
|
|
28 |
;<source> <destination>
|
|
|
29 |
"\epoc32\release\armv5\urel\hscontentcontrolexample.exe" -"!:\sys\bin\hscontentcontrolexample.exe"
|
|
|
30 |
"\epoc32\data\z\resource\apps\hscontentcontrolexample.r01" -"!:\resource\apps\hscontentcontrolexample.r01"
|
|
|
31 |
"\epoc32\data\z\private\10003a3f\apps\hscontentcontrolexample_reg.r01" -"!:\private\10003a3f\import\apps\hscontentcontrolexample_reg.r01"
|
|
|
32 |
"\epoc32\data\z\resource\apps\hscontentcontrolexample_aif.mif" -"!:\resource\apps\hscontentcontrolexample_aif.mif"
|
|
|
33 |
"\epoc32\data\z\resource\apps\hscontentcontrolexample.mbm" -"!:\resource\apps\hscontentcontrolexample.mbm"
|
|
|
34 |
; Add any installation notes if applicable
|
|
|
35 |
;"hscontentcontrolexample.txt" -"!:\private\0xE88D7143\hscontentcontrolexample.txt"
|
|
|
36 |
|