Tinny Ng wrote:
> So far here is what I understand from Murray's proposal:
>
> Proposed changes to be made in the Xerces-C Project
> =====================================
> 1. Xerces-C source code: all #include insides the headers (e.g.
> DOMParser.hpp) and the source files (e.g. DOMParser.cpp)
> will be modified with 'xercesc' added, e.g.
> #include <xercesc/dom/DOM.hpp>
> And the samples, build instruction, perl script, Makefiles, project
> files that part of the Xerces-C will all be modified
> together.
>
> 2. Binary distribution: include folder rename from
> $XERCESCROOT/include/<subfolders> to
> $XERCESCROOT/include/xercesc/<subfolders>
>
> 3. CVS tree and thus source distribution: src folder rename
> from $XERCESCROOT/src/<subfolders> to
> $XERCESCROOT/xercesc/<subfolders>
[snipped]
> Yes we need (to do #3). For users who build from CVS tree or
> source distribution directly, the "include" folder
> does not exist at all. So if we only do #1 and #2 without #3, then
> users who build from CVS tree directly will for sure be broken.
[snipped]
> So if we cannot keep the revision history after the rename, then I
> would vote -1 for this proposal.
>
> Tinny
Just a thought ....
We need to rename <src> to <xercesc> because we need to take care of those
users who build from CVS / source distribution directly where the "include"
folder does not exist. They will be broken after 'xercesc' is added to
all #include => #include <xercesc/dom/DOM.hpp>.
I am thinking how about we create a new "include/xercesc" folder in the CVS
directly, and then separate and move all the headers (.h, .hpp and .c) from
"src" to this new folder "include/xercesc".
If we do this, then we don't need to rename src to xercesc. And all the
source files (.cpp) remain in its original "src" directory, only the
headers are moved and thus only the CVS revision history of headers are
lost, which is less "scary"
....
But on the other hand, relative path include from the src folder directly
like #include "./DOMException.hpp" or #include "../util/XMLString.hpp"
won't work ...
Just a fuzzy second thought on Friday afternoon ...... don't yell if you
don't like it ..... :-)
Tinny
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
