[lxml-dev] Building 0.6 on Windows

I just tried building the 0.6 release on Windows, using the Win32 libxml distribution from: http://www.zlatkovic.com/libxml.en.html Fixing the setup file was pretty trivial, the behaviour when Pyrex wasn't installed was a bit surprising (but easy to fix), but I've now stumbled upon a more annoying problem -- the output from Pyrex doesn't include any "include" statements for libxml and libxslt, so building doesn't work that well. cd lxml-0.6/src/lxml/ grep -n include *.c NUL etree.c:3:#include "Python.h" etree.c:4:#include "structmember.h" etree.c:14272:#include "compile.h" etree.c:14273:#include "frameobject.h" etree.c:14274:#include "traceback.h" Has anyone seen this before? Are there any more includes in the sources on a successful build? Should the C sources perhaps be included in the source distribution, so you can build without Pyrex if you don't plan to hack on the code? </F>

Hey Fredrik, Nice to see you post on the list! Fredrik Lundh wrote:
Not to my knowledge, though I myself haven't tried building it on Windows. Jeff Gayle sent me a successful windows built though that seemed to work for some others (for an older version of lxml). I'll forward what he sent to me in a private followup. I'd very much like to get contributions so this builds more straightforwardly on Windows, plus of course the windows builds themselves so I can host them on the site. Jeff Gayle made a great start, but if you could chip in that would be wonderful. :)
Yes, they should be, and Julien Anguenot offered to work on this, so I'm waiting for his setup.py work. But let's not wait for him if you can go faster. :) Regards, Martijn

Fredrik Lundh wrote: [snip]
This is weird, it does so in my case: 3:#include "Python.h" 4:#include "structmember.h" 8:#include "stdio.h" 9:#include "libxml/encoding.h" 10:#include "libxml/tree.h" 11:#include "libxml/xmlIO.h" 12:#include "libxml/xmlstring.h" 13:#include "libxml/xmlerror.h" 14:#include "libxml/parser.h" 15:#include "libxml/xpath.h" 16:#include "libxml/xpathInternals.h" 17:#include "libxslt/xsltInternals.h" 18:#include "libxslt/transform.h" 19:#include "libxslt/xsltutils.h" 20:#include "libxml/relaxng.h" 21:#include "libxml/c14n.h" 22:#include "stdlib.h" 12779:#include "compile.h" 12780:#include "frameobject.h" 12781:#include "traceback.h" Some issue with Pyrex versions perhaps? The includes are generated from information available in the various .pxd files. Regards, Martijn

Hey Fredrik, Nice to see you post on the list! Fredrik Lundh wrote:
Not to my knowledge, though I myself haven't tried building it on Windows. Jeff Gayle sent me a successful windows built though that seemed to work for some others (for an older version of lxml). I'll forward what he sent to me in a private followup. I'd very much like to get contributions so this builds more straightforwardly on Windows, plus of course the windows builds themselves so I can host them on the site. Jeff Gayle made a great start, but if you could chip in that would be wonderful. :)
Yes, they should be, and Julien Anguenot offered to work on this, so I'm waiting for his setup.py work. But let's not wait for him if you can go faster. :) Regards, Martijn

Fredrik Lundh wrote: [snip]
This is weird, it does so in my case: 3:#include "Python.h" 4:#include "structmember.h" 8:#include "stdio.h" 9:#include "libxml/encoding.h" 10:#include "libxml/tree.h" 11:#include "libxml/xmlIO.h" 12:#include "libxml/xmlstring.h" 13:#include "libxml/xmlerror.h" 14:#include "libxml/parser.h" 15:#include "libxml/xpath.h" 16:#include "libxml/xpathInternals.h" 17:#include "libxslt/xsltInternals.h" 18:#include "libxslt/transform.h" 19:#include "libxslt/xsltutils.h" 20:#include "libxml/relaxng.h" 21:#include "libxml/c14n.h" 22:#include "stdlib.h" 12779:#include "compile.h" 12780:#include "frameobject.h" 12781:#include "traceback.h" Some issue with Pyrex versions perhaps? The includes are generated from information available in the various .pxd files. Regards, Martijn
participants (2)
-
Fredrik Lundh
-
Martijn Faassen