Here's a tarball of a Xerces-C++ with the discussed changes:
http://www.murrayc.com/temp/xercesc_sane_includes.tar.gz
Apparently I'm supposed to upload this to the 'experimental folder'.
Maybe somebody could do this or tell me where that folder is.
I expect that we still need to make minor include path changes to
project files such as the MS Visual C++ and Borland project files, but I
don't have the setup for that.
Here's a recap:
What does this give you?
- You may now do this:
#include "xercesc/somefolder/someheader.h"
instead of this:
#include "somefolder/someheader.h"
- This should prevent clashes with headers of the same name, as well as
making your code clearer.
What do you need to do differently?
- Either
a) Change your #include lines to contain 'xercesc/'. This is the best
choice in the long term.
or b) Change the include path in your build files/projects:
- if your include path is e.g.
/home/murrayc/xercescdownload/include,
then change it to
/home/murrayc/xercescdownload/include/xerces.
- if your include path is /usr/local/include then change it to
/usr/local/include/xercesc.
- Be careful if using /usr/include. With gcc, you probably shouldn't
specify this yourself because it is an implict include path, and
specifying it seems to override other implicit include paths.
- This will be supereasy in future if we provide a command-line script
which our build files can call to get the appropriate include and
linking arguments.
What changes were made to achieve this?
- The src directory was renamed to xercesc.
- Makefile.incl files were changed to copy into ../include/xercesc
instead od ../include
- Makefile.incl files were changed to use the appropriate include path.
- All #includes in the code were changed to use "xerces/" where
necessary.
How will we integrate these changes again later:
- Just rename xercesc back to src, create a diff, apply the diff to the
up-to-date code, and rename src to xercesc.
- The changes are simple and they are in parts of the files which are
unlikely to be touched by other work.
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
Murray Cumming wrote:
>
> Tinny Ng wrote:
> >
> > According to your summary of count, if we count committers votes only,
> > then we don't have any vetos, but we also don't have enough 3 binding +1
> > votes. If we count all users' votes, we have enough 3 +1 votes, but then
> > there are -1s as well ....
> >
> > Anyway, I think Jason's suggestion sounds good. Put the source tar in the
> > experimental folder and let people play with it for a couple of months.
> > Set a deadline for testing period. If no complaints, then put into CVS
> > later after the deadline ....
>
> OK. I will do that. Thank you.
>
> I just asked, because I thought that you were saying that I had to do
> some more lobbying. Nevermind.
>
> > Tinny
> >
> > Murray Cumming wrote:
> >
> > > Tinny Ng wrote:
> > >
> > > > If there is any veto, and if you disagree
> > > > with the veto, you should lobby the person who cast the veto. Until
> > > > all vetos are resolved, then we can move on from there.
> > > >
> > > > Tinny
> > >
> > > Are there any vetos?
> > > == Are there any -1s from committers?
> > >
> > > --
> > > Murray Cumming
> > > www.murrayc.com
> > > [EMAIL PROTECTED]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> Murray Cumming
> www.murrayc.com
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
