Hi, Christian Zagrodnick wrote:
On 2008-02-09 14:33:43 +0100, Christian Zagrodnick <cz@gocept.com> said:
On 2008-02-08 20:43:18 +0100, Stefan Behnel <stefan_ml@behnel.de> said:
Christian Zagrodnick wrote:
The main problem is, that lxml runs the wrong xslt-config. So I was basically building libxml2 and libxslt just for the fun of it.
The question is if lxml really always needs to call xslt-config. Or how one would set the path in the buildout so that the right xslt-config is called.
If I manually set the path it works like charm:
% PATH=`pwd`/parts/libxslt/bin:$PATH bin/buildout You can now pass "--with-xslt-config=XXX" to setup.py.
... and --with-xml2-config=YYY, just in case you installed both in different places.
Gotta check how we best pass that along in buildout.
So in the *next* version of zc.recipe.egg (i.e. >1.0.0), the following will probably work. It works with the trunk of zc.recipe.egg (but this is neither released nor has it been reviewed by Jim Fulton, yet):
[lxml-environment] PATH=${buildout:directory}/parts/libxslt/bin:%(PATH)s [...]
... and, you can also set the XML2_CONFIG and XSLT_CONFIG environment variables to make sure setup.py really picks up the right config. Stefan