Re: Help getting lxml to work reliably on MacOS-X

On 2008-02-09 14:33:43 +0100, Christian Zagrodnick <cz <at> gocept.com> said:

> On 2008-02-08 20:43:18 +0100, Stefan Behnel <stefan_ml <at> behnel.de> said:
> 
>> Hi,
>> 
> 
>> 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.
> 
> 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):

[libxml2]
recipe = zc.recipe.cmmi
url = http://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/libxml2-2.6.30.tar.gz
extra_options = --without-python

[libxslt]
recipe = zc.recipe.cmmi
url = http://ftp.gnome.org/pub/GNOME/sources/libxslt/1.1/libxslt-1.1.22.tar.bz2
extra_options = --with-libxml-prefix=${buildout:directory}/parts/libxml2/
                --without-python

[lxml-environment]
PATH=${buildout:directory}/parts/libxslt/bin:%(PATH)s

[lxml]
recipe = zc.recipe.egg:custom
egg = lxml
include-dirs = ${buildout:directory}/parts/libxml2/include/libxml2
               ${buildout:directory}/parts/libxslt/include
library-dirs = ${buildout:directory}/parts/libxml2/lib
               ${buildout:directory}/parts/libxslt/lib
rpath = ${buildout:directory}/parts/libxml2/lib
        ${buildout:directory}/parts/libxslt/lib
environment = lxml-environment

Regards,
--

-- 
Christian Zagrodnick

gocept gmbh & co. kg  ·  forsterstrasse 29 · 06112 halle/saale
www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891