Instead of using the WixToolPath variable I found that I can use the
WIX environment variable.
I set my additional linker options to:
-ext WixDifxAppExtension -ext WixUIExtension $(WIX)bin\difxapp_x86.wixlib
This works like a charm.
- Kim
--
*Kim Gybels
Software Developer
*
That means it wasn't finding the .wixlib. Can you paste the light.exe
command line it's running?
The light.exe command line does not mention the wixlib, although it
is shown in the tree view of my setup project.
You can't use WixToolPath in the additional options because that's a
property
Kim Gybels wrote:
The light.exe command line does not mention the wixlib, although it
is shown in the tree view of my setup project.
Check its properties to make sure it's not marked to include in the output.
So all variables get expanded when the property is created and
not when the
Bob Arnson wrote:
Kim Gybels wrote:
I have these additional linker options set:
-ext WixDifxAppExtension -ext WixUIExtension C:\Program Files\Windows
Installer XML v3\bin\difxapp_x86.wixlib
You can add those files to your project and avoid using any additional
linker options value.
Kim Gybels wrote:
That doesn't work, I get the following:
Error11Unresolved reference to symbol
'CustomAction:MsiProcessDrivers' in section 'Fragment:'.
That means it wasn't finding the .wixlib. Can you paste the light.exe
command line it's running?
You can't use WixToolPath in
Kim Gybels wrote:
I have these additional linker options set:
-ext WixDifxAppExtension -ext WixUIExtension C:\Program Files\Windows
Installer XML v3\bin\difxapp_x86.wixlib
You can add those files to your project and avoid using any additional
linker options value.
--
sig://boB
6 matches
Mail list logo
