Hey Jay,

On 15/03/2008, Jay Berkenbilt <[EMAIL PROTECTED]> wrote:
> "Jason Stewart" <[EMAIL PROTECTED]> wrote:
>
>  > I was curious why xerces-p would be a casualty? The primary struggle
>  > I've had as xerces-p maintainer was xerces-c's alternate build system.
>  > Now that it fully supports the GNU toolchain, xerces-p is bundled with
>  > xerces-c as a subproject. Shouldn't that make it easier for debian?
>
>
> Oh, I didn't realize it was bundled with xerces-c now, or has it been?
>  In that case, there should be no problem.
>
>  (looking at the distribution)
>
>  Hmm.  I don't see it.  Am I missing something?  Where can I get a
>  xerces-p that will work with 3.0.0?
>

It was not included with the beta, it is in subversion under the
swig/perl/ directory. There is one bug that is currently keeping it
from compiling due to my ignorance of autoconf/automake.

If the Xerces-C team thinks it's valuable to include Xerces-P, then it
will make it into the release.

>  > I don't think there are many active users of xerces-p, so if it was
>  > dropped out of debian, those that wanted it could get it from CPAN.
>
>
> True enough.  Anyway, I'll keep it in if I can.  I just didn't realize
>  there was a version that worked with > 2.7.0.  My source of
>  information is the Xerces P link on xerces.apache.org.  I also see
>  that 2.7.0 is the latest version on CPAN.
>
>  For what it's worth, I made a quick attempt to package XML::Xerces
>  2.7.0 with 2.8.0, and the configuration complained that the versions
>  didn't match.  I didn't make any attempts to override it.
>

Xerces-p is built by running swig on the latest version of Xerces-C
and then compiling the swig-generated .cpp files against the xerces-c
library.

In my experience as maintainer from the Xerces-C 1.x until now - there
have been changes in the header files that make it impossible to
compile swig-generated source files from a previous release against
the library from the latest release. Therefore I added the simple
check against the version number - if it fails to find the version it
expects it issues a warning. We used to get a lot of complaints on the
list with people trying to build old xerces-p releases against newer
xerces-c libraries.

Cheers, jas.

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

Reply via email to