Not sure I can provide any help for you, but I wanted to ask a few questions out of curiosity: - Why do you want a dynamically linked version? - Why can't you use the already existing binaries? Oh, one reason why the build might be failing for you is that you are trying to use libxml 2.6.x, and we depend on 2.7.x? On Wed, Oct 29, 2008 at 7:46 AM, Cserna, Zsolt (IT) <Zsolt.Cserna@morganstanley.com> wrote:
Hi all,
I'm trying to build lxml 2.1.2 for python 2.5 on windows, but the linking fails with the following error:
lxml.etree.obj : error LNK2019: unresolved external symbol _xsltProcessOneNode referenced in function ___pyx_pf_4lxml_5etree_13XSLTExtension_apply_templates
I would like to link the libxml and the other libraries to lxml dynamically, not statically. Is it possible? It seems to me that xsltProcessOneNode is not defined in the windows version of libxslt (btw it's not defined in any .h files), however it's defined in unix .so files.
I've installed all the dependencies, libxml version 2.6.31, libxslt 1.1.22, zlib 1.2, iconv 1.9, and using VC7.1 for building.
Could you please advice on this?
Any help/ideas would be appreciated.
Thanks,
Zsolt --------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. _______________________________________________ lxml-dev mailing list lxml-dev@codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev
-- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 Skype zopedc