Jason E. Stewart wrote:

Hey All,

I've finally solved the namespace compilation issues that crept up in
Xerces-C-2.2 - just in time to make a release for Xerces-C-2.3!

Thank you so much! Finally it compiles (quasi out of the box, without running SWIG). This is Win2000, Perl 5.6.1 and VC 6.0.


A few issues concern "makefile.pl":
"config.status" is not included in the xerces-c Windows binaries.

my $LIBXERCES = "-lxerces-c_2";
# this is the library name on Windows

my $CFLAGS = '-D_REENTRANT -DWIN32 -TP -GX -DHAS_BOOL';
# with config.status missing $CFLAGS are undefined

\$(MAKE) -C Handler static
# this syntax doesn't work on Windows, replace with:
cd Handler && \${MAKE} static

For some reason, Xerces.C isn't compiled by the makefile. I had to compile it by hand.

Testing: All tests fail unless the system path is set to include the location of Xerces-c_2_3_0.dll. Some of the tests fail because of unix syntax in the test files (like "2>/dev/null"). Exception handling seems particularly weak (tests fail mainly on exceptions). The message is always "Handling Unknown exception".

Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t\AttributeList.t 3 768 8 3 37.50% 5-7
t\Attributes.t 4 1024 14 4 28.57% 8 10-11 14
t\DOMCount.t 1 256 2 1 50.00% 2
t\DOMCreate.t 1 256 2 1 50.00% 2
t\DOMDocument.t 2 512 35125 2 0.01% 3-4
t\DOMException.t 6 1536 7 6 85.71% 2-7
t\DOMPrint.t 1 256 2 1 50.00% 2
t\SAX2Count.t 4 1024 5 4 80.00% 2-5
t\SAXCount.t 4 1024 5 4 80.00% 2-5
t\SAXException.t 255 65280 6 5 83.33% 2-6
t\Schema.t 255 65280 3 1 33.33% 3
t\URLInputSource.t 2 512 8 2 25.00% 6 8
t\XMLException.t 1 256 1 1 100.00% 2
12 subtests skipped.
Failed 13/35 test scripts, 62.86% okay. 34/35353 subtests failed, 99.90% okay.


Hope this helps - currently I don't have time to investigate further.

Martin



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



Reply via email to