"Jason E. Stewart" wrote:
> 
> "Mark Weaver" <[EMAIL PROTECTED]> writes:
> 
> > I would find this change extremely welcome.  The current random header file
> > location is annoying, to put it mildly, plus prone to potential collisions.
> >
> > This would seem to be the right place to post, but finding an active
> > committer here willing to take on changes seems to be rather a challenge!
> 
> You should first take a look at the work the Murray has done. This
> should address many of these issues.
> 
> jas.
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: message/rfc822

Having include files installed as shown there is a major improvement,
e.g., to /usr/include/xercesc/. There are other issues I'm interested in
in addition to this, for simplification of config without setting
environment variables. But in either case, is it possible to get
something merged into the official distribution? Xerces is a major
barrier when it comes to projects that are to be distributed in source
form and then compiled by average Linux users (versus developers). Being
able to install Xerces headers would remove the XERCESCROOT setting
quite nicely, but there are other specifications that simplification
would also aid.

I hear a lot of people shout about the use of automake/autoconf/libtool
for cross platform configuration, but when doing C++, autoconf and
friends are basically broken; mix C and C++, those tools are a disaster.
So I am not suggesting conversion to some big configuration tool, but
even the basic Makefiles involved tend to be a barrier when writing
packages that will depend upon Xerces. Some simple things could be done,
such as offering sane default values for some unset variables. Xerces is
an amazing piece of work, I'm surprised that configuration and
installation is so far behind the actual code. If users get frustrated
by it, and can't or won't use it, then it does no good for anyone.

D. Stimits, [EMAIL PROTECTED]

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

Reply via email to