DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25970>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25970

Xcode project file for Xerces C++ fails to build because uses wrong compiler

           Summary: Xcode project file for Xerces C++ fails to build because
                    uses wrong compiler
           Product: Xerces-C++
           Version: 2.4.0
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Build
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


The Xerces C++ source distribution includes project files that work with XCode, 
Apple's latest IDE.  
When the XercesLib project is built in XCode, the compile fails when the compiler 
crashes.  This 
problem occurs with both XCode 1.0 (released in September) and XCode 1.1 (released in 
December.)  This problem does not occur if Xerces-C++ is built using Makefiles from 
the 
command line.

The cause of this bug is that the project file specifies that GCC-2.95 is used as the 
compiler.  
Specifically, the active build style is set to "Development GCC2".  The active build 
style should 
instead be set to "Development GCC3" so that the project is built with the latest 
gcc-3.3 compiler.

To change the active build style and enable XercesLib to be compiled:
* Launch XCode and open the XercesLib project file.
* Select the icon for the XercesLib project in XCode's "groups and files" tree view 
(top item in the 
list)
* Press command-i to raise the Project Info dialog box.  
* Switch to the Styles tab
* Change the active build style to Development GCC3.
* Quit XCode.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to