DK created XERCESC-1989:
---------------------------

             Summary: Xerces 3.1.1 Xerces.Lib fails to build with new Visual 
Studio 2012 RC
                 Key: XERCESC-1989
                 URL: https://issues.apache.org/jira/browse/XERCESC-1989
             Project: Xerces-C++
          Issue Type: Bug
          Components: Build
    Affects Versions: 3.1.1
         Environment: Windows 7, new Visual Studio 2012 RC. Building x86 
XercesLib.
            Reporter: DK
            Priority: Minor


Error during resource compile. I raised it as an issue with MS Connect and the 
response states that it is due to a change in "winnt.h" where previous warning 
messages are now error messages.

Text from MS reply is:

The reason this is a build error now, instead of a build warning, is due to a 
change in winnt.h.  If you look at line 141, you'll reach the #error statement 
on this line because none of the architecture constants are defined.

There are a couple of ways to work around this build error, in order of 
preference:

1.  Remove the #include <winnt.h> statement from your .rc files if it's not 
needed.
2.  Replace the #include <winnt.h> statement with #include <windows.h> or 
#include <winnt.rh>
3.  If you really need to keep the #include <winnt.h> statement in place, you 
can define one of the architecture constants before the #include line, for 
example:
#define _X86_
#include <winnt.h>

I have tested '2' by changing 'winnt.h' to 'winnt.rh' on lines 11 & 87 in 
xerces-c-3.1.1\src\xercesc\util\MsgLoaders\Win32\Version.rc and it now compiles 
and links without error.

Obviously, your choice of option suggested by MS that you wish to employ.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to