"Murray Cumming" <[EMAIL PROTECTED]> writes:
> "Arnold, Curt" wrote:
> >
> > I haven't been following this thread and it troubles me that
> > appears that it would require touching every single include of a
> > Xerces header file at least in applications (and possibly in the
> > Xerces code base itself)?
>
> No, I have said several times that this will not require any existing
> apps to change the way that they #include the Xerces-C++ headers. Read
> the thread.
>
> And I don't see the point in complaining that it will be necessary to
> change part of the Xerces-C++ code base. Of course it needs to be
> changed to be fixed.
Murray,
People don't get it. This isn't a clear issue of 'we can't compile',
'I can't like my app', or 'there's a memory leak'. So please be
patient with them.
You've done this before, but if you want people to care about this
issue, it looks like you'll have to do it again. Summarize what's
broken and how this solution will fix it.
> However, until we fix the build issues then Xerces-C++ will:
> - Never be easy to install.
> - Never be provided with Linux distributions.
It would be big win to have 'configure ; make ; make install'
working.
However, Xerces-C is already in the debian distro and has been for some
time. I still think we should make it easier to install.
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
