[xslt] "Re: libxslt with thread-enabled libxml2?"
- From: Kasimier Buchcik <kbuchcik 4commerce de>
- To: <xslt gnome org>
- Subject: [xslt] "Re: libxslt with thread-enabled libxml2?"
- Date: Mon, 14 Apr 2003 12:29:42 +0200
Hi,
On Fri, 11 Apr 2003 20:17:52 +0200, Igor Zlatkovic wrote:
> That being said, as I see it, you used the multi-threaded libxml for
> linking libxslt, but you used single-threaded libxml headers when
> compiling libxslt. By that, I mean LIBXML_THREAD_ENABLED was not
> defined. Can that be?
Well, maby I did domething wrong. Here is what I performed:
libxml2 (ver. 2.5.4)
cscript configure.js threads=native prefix=<MY_XML_INSTALL_DIR>
include=<MY_ICONV_DIR>\include lib=<MY_ICONV_DIR>\lib
nmake
libxslt (ver. 1.0.27)
cscript configure.js prefix=<MY_XSLT_INSTALL_DIR>
include=<MY_XML_INSTALL_DIR>\include;<MY_ICONV_DIR>\include
lib=<MY_XML_INSTALL_DIR>\lib
nmake
I guess or hope that libxslt has taken the headers of the previously
builded multi-threaded libxml, since it was pointed to that include
folder. Additionally I did not find LIBXML_THREAD_ENABLED in the libxslt
sources. So I wonder if that would make some difference to the
compilation of libsxlt, if this is what you meant. I would be glad if
someone could send me some info about how to build those dlls properly.
On Fri, 11 Apr 2003 18:06:00 -0400, Daniel Veillard wrote:
> My initial mail is just ...
> "I'm gonna make --enable-thread the default compilation switch on Linux
> and I'm asking for possible problems at the libxslt level..."
> If it works, then fine
I'm not sure if this works. *If* I performed the build of libxslt the
way it was intended, then something needs to be changed.
We originally implemented thread safety at the application level, but
were curious about switching to libxml2 thread support. The problem is:
we cannot run the multi-threaded libxml2.dll in conjunction with the
straight forward builded libxslt.dll. We get some complains about a non
existent xmlGenericError entry point;
"libxml2-2.5.4\win32\libxml2.def.src" declares the export of
__xmlGenericError and not xmlGenericError if LIBXML_THREAD_ENABLED is
on). As far as I am concerned "xmlGenericError" is used extensively in
the libxslt sources.
Thanks and greetings,
Kasimier Buchcik
--
4commerce technologies
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]