Hi,

Ignore my mail; after looking to the matter, instead of listing to one of my
developers, the issue has nothing to do with the use of Ansi or Unicode!

The library reference to Version.lib seems to be gone, so I assume the all
the library references should be added into our CA project; by doing so the
problem is fixed..

Sorry; didn't had time yet for my coffee this morning...

Albert van Peppen

-----Oorspronkelijk bericht-----
Van: Albert At School [mailto:alb...@de-notenbalk.nl] 
Verzonden: maandag 26 april 2010 10:29
Aan: 'General discussion for Windows Installer XML toolset.'
Onderwerp: [WiX-users] WiX 3.5 dutil.lib build

Hi,

Why is there a sudden change in building the libs?
In the wix-3.5.1623.0 the libs are build with Unicode while before they did
not?

I am compiling my CA DLLs (build in native C++) with non Unicode and after
updating today to the build 1623 gives me the following link errors:

1>dutil.lib(fileutil.obj) : error LNK2001: unresolved external symbol
_verqueryval...@16
1>dutil.lib(fileutil.obj) : error LNK2001: unresolved external symbol
_getfileversionin...@16
1>dutil.lib(fileutil.obj) : error LNK2001: unresolved external symbol
_getfileversioninfosi...@8
1>L:\Projects\bin\ReleaseStatic\vc90\Win32\_D4WMSI.dll : fatal error
LNK1120: 3 unresolved externals

While in previous versions there where no problems.

If there was a change from Ansi to Unicode I might expect it to be noticed
in the changes.
Also, why not build/supply both libraries then?

Regards,

Albert van Peppen
Senior System Engineer
Insad Grafisch b.v.



----------------------------------------------------------------------------
--
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to