I am very much interested in having xerces-p for Windows, but haven't had complete success yet. Here are some findings, maybe someone can shed additional light on the problems.
XML-Xerces-2.0.0-3 doesn't compile out of the box. Firstly this is due to some incompatibilities in Makefile.PL which can be overcome by hand (such as replacing unix-specific "make" and "find" syntax, compiler flags and the xerces-c library name). For some reason "xerces.C" is not made (because of the uppercase ".C" it seems) and has to be compiled by hand.
Problems arise in the linking phase. The resulting .obj file can't be linked against the Xerces-C.lib Version 2.0.0, because some vital symbols are not exported in the Win32 binary distribution (e. g. SaxNotSupportedException). Perhaps rebuilding the Xerces-C library from the source would help - I haven't tried yet.
So I tried to rebuild the whole module using Swig-1.3.17 against the Xerces-C.lib Version 2.2.0 (which contains the missing symbols). This also proved rather difficult because of the "xercesc" namespace that has been introduced meanwhile: I had to insert the corresponding prefixes into the *.hpp files in the "Handler" subdir and in Xerces.C. Afterwards the module compiled and linked OK into a DLL.
Xerces.pm would compile only after adjusting "postmodule.pl" (adding a fragment from XML-Xerces-1.7.0-1. which inserts
"use vars qw(@ISA %OWNER %ITERATORS %BLESSEDMEMBERS)" into each package). Still all tests fail because SWIG doesn't seem to generate a "new" method for "PerlErrorCallbackHandler". This is where I'm stuck for the moment.
Any ideas?
Thanks,
Martin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
