The following comment has been added to this issue:
Author: Adam Heinz
Created: Mon, 20 Sep 2004 1:44 PM
Body:
1. Sure, no problem.
2. I link against the entire library, so it doesn't seem unreasonable to have the
entire library at my disposal at compile time. I add Xerces.hpp to my precompiled
header and never think about including another Xerces header. Fast compiles, too.
Since Xerces has been namespaced since 2.2.0, if I make sure to put it first in my
.pch, I never have to worry about the other sloppy libraries I am forced to use
trashing Xerces' environment.
adam
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/XERCESC-1266?page=comments#action_53259
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1266
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESC-1266
Summary: need framework headers for Mach-O
Type: Bug
Status: Unassigned
Priority: Major
Project: Xerces-C++
Components:
Build
Versions:
2.5.0
Assignee:
Reporter: Adam Heinz
Created: Thu, 26 Aug 2004 6:46 AM
Updated: Mon, 20 Sep 2004 1:44 PM
Environment: CodeWarrior 8.3, MacOS 10.2
Description:
In the Macintosh Mach-O architecture, a framework has a single header file that
includes all headers for the entire shared library. Since we already have a DOM.hpp
that includes the contents of the /dom dir, I propose adding a similar header to each
of the other dirs and a Xerces.hpp header at the top level that would include these
headers.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
