Hi Merlin,
I am posting this message to xalan-c-users and copying you. Please join
the mailing list, since that's the best place to post questions about
Xalan.
Xalan 1.3 was built against Xerces 1.6. You will not be able to build
Xalan 1.3 against Xerces 1.7 as there are incompatible header files changes
in Xerces. Since I ran the latest Xalan, which is built against Xerces
2.0, and there are no longer any errors, I would suggest you upgrade to the
latest CVS code of Xalan and get the Xerces 2.0 distribution.
If you don't want to apply the Dinkumware patches, you can apply MSVC++
service pack 5, which has fixes for the library problems. Then, build the
latest Xalan sources. If you already have SP 5, you are all set -- just
build the latest sources.
Using the distribution binaries _without_ applying the Dinkumware patches
is a recipe for distaster, so I would suggest you go one way or the other.
To use the distribution binaries you must have MSVC++ with SP3 and the
Dinkumware patches.
I hope that makes sense to you. If not, please post a reply to the mailing
list, and I'll try to answer any questions you may have.
Dave
"Merlin Moncure"
<[EMAIL PROTECTED] To:
t.com> cc:
Subject: xml-xalan
07/30/2002 11:38
AM
For some reason, bugzilla did not get my response (I'm new to it), so I'm
sending it to you directly.
You were correct, I was reporting about the namespace errors, which xalan.
exe writes to stderr.
The standard xalan distro comes with xerces 1.6 built into it. Since I am
minus dinkumware, I did not build xalan and used the provided dlls.
I never used xerces 1.6, and can not find a copy outside of xalan distro,
so I can't directly confirm if the problem is from xerces parser. Of
course, If this Is the source of the problem, its not really a bug but more
of a 'todo'.
I tried leap of faith dll switch to new xerces parser and that did not work
(naturally). For a challenge during off work hours I might try and build
xalan with 1.7. My chance of success here depends on the extent the api
changed between those versions. I did not check the nightly build of
xalan.
Mircosoft's stl errors make me hesitant to recompile xalan here at work
since it uses a lot of templates (unlike xerces), I'm afriad I might
introduce quirks to my soon to be production server.
Thanks for your quick response.
Merlin
