Qt Smart Installer pkg and non-root sis files

[tamhanna]

Hello Folks,
I have just stumbled across something weird in relation to the SmartInstaller.

The pkg file it creates for deployment looks like this:

; QtBallZ_installer.pkg generated by qmake at 2010-02-26T17:08:51
; This file is generated by qmake and should not be modified by the user
;

; Language
&EN

; SIS header: name, uid, version
#{"QtBallZ installer"},(0xA000D7CE),1,0,0

; Localised Vendor name
%{"Vendor"}

; Unique Vendor name
:"Vendor"


; Manual PKG pre-rules from PRO files
; Default HW/platform dependencies
[0x101F7961],0,0,0,{"S60ProductID"}
[0x102032BE],0,0,0,{"S60ProductID"}
[0x102752AE],0,0,0,{"S60ProductID"}
[0x1028315F],0,0,0,{"S60ProductID"}
 
; Default dependency to Qt libraries


"C:/Symbian/Carbide/workspace/QtBallZ/QtBallZ.sis" - "c:\adm\QtBallZ.sis"
@"C:/Qt/4.6.2/smartinstaller.sis",(0x2002CCCD)

My issue is the bold line. I have Qt set up to dump all sis files into /sis/, and always have to edit the pkg by hand now. Anyone have any intentions or ideas re this?

Tam

P.S. Workstation: WinXP Pro. Qt: 4.6.2 Carbide: 2.4

[ltomuta]

This should be easy to fix although I've never tried to redirect the *.sis output to a non-default location. How do you do that using Qt settings?

[tamhanna]

Hi Lucian,
its a crooked trick, I admit.

Project -> Properties -> Carbide -> BuildConf -> SIS Builder. Edit sis, and make output file name be sis\TypeGun.sis

Tada

Tam

[hamishwillee]

Consider
#{"QtBallZ installer"},(0xA000D7CE),1,0,0

I can change the values of this through:
DEPLOYMENT.installer_header = 0x12345678

Can you confirm that I must do so - at least for the UID?

[ltomuta]

Hi Hamish,

I don't think you "have to" but it is good to know that you can change the UID when needed.
The only requirement I know for the pUID is that is must be unique. If it is the same as the one used for the app packaged with it (default in Carbide.c++ and I guess in Qt as well) then it should be fine, since no other app has it.

When developing a plug-in though, which augments and existing installation, the UID of the deployed package may indeed have to be different than the pUID of the package.