Title: Xerces as static Win32 library - once again
Due to the lack of any responses, I've found what appears to be a workaround myself: do not "disable language extensions" in the Visual Studio project for building Xerces as a static library. At least this makes the aforementioned compile errors go away.
 
Anybody has a clue why the XercesLib that comes with the Xerces distribution has no problems, although it is set to "disable language extensions"?
 
I still wonder why the fix that John Clayton provided is not part of 1.6.0. It would be quite convenient if something like this was checked into Xerces' source base, such that I wouldn't have to start from scratch every time I download a new version. Moreover, a number of Xerces users seems to have the same need for building Xerces as a static (Win32) library. So, what's holding it back?
 
Regards,

Peter Bertelsen
Maconomy R&D
http://www.maconomy.com

-----Original Message-----
From: Peter Michael Bertelsen [mailto:[EMAIL PROTECTED]]
Sent: 11. december 2001 19:52
To: Xerces-C Mailing List (E-mail)
Subject: Xerces as static Win32 library - once again

Hi,

I've been trying to follow the guidelines that John Clayton gave earlier on this topic.
(See http://marc.theaimsgroup.com/?l=xerces-c-dev&m=100590213927031&w=2 for details.)
However, when compiling my XercesStaticLib, I keep getting errors in winnt.h like these:

  ...\VC98\INCLUDE\winnt.h(357) : error C2467: illegal declaration of anonymous 'struct'
  ...\VC98\INCLUDE\winnt.h(376) : error C2467: illegal declaration of anonymous 'struct'
  ...\VC98\INCLUDE\winnt.h(1519) : error C2146: syntax error : missing ';' before identifier 'PVOID'
  ...\VC98\INCLUDE\winnt.h(1519) : error C2501: '_inline' : missing storage-class or type specifiers
  ...\VC98\INCLUDE\winnt.h(1519) : fatal error C1004: unexpected end of file found

Has anybody else experienced something similar? If so, what was the cure?

BTW, what was the reason for not including John's fix in 1.6.0?

TIA,
Peter Bertelsen
Maconomy R&D
http://www.maconomy.com

Reply via email to