Ok, so renaming my wixpdb files, produced as described above, to wixout
extension solved the problem for torch input and it produced wixmst
output file. Thus, apparently, wixpdb can exist only in XML format,
while wixout is binary.
Based on Peter Marcu's blog I understood that wixpdb substitutes
With just -bf and -xo as additional linker options Votive creates this
command line:
C:\Program Files\Windows Installer XML v3\bin\Light.exe
-loc CustomWixUI_en-us.wxl
-out C:\path\Product.msi
-pdbout C:\path\Product.wixpdb -bf -xo
obj\Debug\BrowseDlg.wixobj
... dialog and other wixobjs ...
Yup, that will do it.
From: Justin Goshi
Sent: Wednesday, October 31, 2007 11:12 AM
To: Peter Marcu; wix-users@lists.sourceforge.net
Subject: RE: Torch error
Yup, there are differences in the table definition for WixFile between the two
wixouts. It's because my base image wixout was generated b
Yup, there are differences in the table definition for WixFile between the two
wixouts. It's because my base image wixout was generated by the old Wix build,
and the new wixout has an additional PatchAttributes column in the WixFile
table.
Thank you for your help!
Justin
From: Peter Marcu
Sen
Are there any differences in the table definition for WixFile between the two
wixouts? Can you send just the tale definitions to me?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Goshi
Sent: Wednesday, October 31, 2007 10:36 AM
To: wix-users@lists.sourceforge.net
Subject:
5 matches
Mail list logo
