[lxml-dev] setup.py and buildout
Ian Bicking
ianb at colorstudy.com
Mon Nov 20 23:40:22 CET 2006
Martijn Faassen wrote:
> Hi there,
>
> I reported previously that I created a buildout for lxml, but today I
> found out that is of limited utility: while it correctly links lxml
> against any libxml2 and libxslt library, it does still require the
> libxml and libxstl2 *headers* to be where xslt-config locates them, i.e.
> probably /usr/include
>
> I tried to hack up the setup.py so it would look elsewhere (it is
> supposed to respond to things like --include-dirs), but setup.py has
> grown to be rather complicated. This is a common problem with
> configuring from Python code - it grows all kinds of things which look
> useful but also make it very hard to expect some kind of uniform
> behavior across different systems configuring themselves this way.
>
> I hope that setup.py can still be adjusted so that buildout can be made
> to work. I *think* it's only not responding to --include-dirs that does
> it in.
Luke Tucker has been trying to resolve these same issues in the
Deliverance buildout. I don't know the status -- hopefully he'll chime
in -- but the work is in
http://codespeak.net/svn/z3/deliverance/buildout/trunk
--
Ian Bicking | ianb at colorstudy.com | http://blog.ianbicking.org
More information about the lxml-dev
mailing list