Building lxml statically for MeVisLab

Hi, I'm trying to build lxml for MeVisLab 2.7 on Windows 7 x64. Therefore I'm using the Python 2.7 delivered with MeVisLab and MS Visual Studio 2013 Professional. As my workplace is behind a proxy I had to configure the setup.py and buildlibxml.py to use the already downloaded libraries. How I did this is described in the appended build-changes.txt. So when trying to build lxml it fails with the output in build.log. It looks like it's trying to rebuild lxml.etree, but does it even have to? Would you please help me with this? I don't know what to do from here on. Sincerely, Corbie

Hi, I wrote another mail this week but it seemed to be too confusing. I'm trying to build lxml statically under Windows, but when I do so the script seems to try to build the 'lxml.etree' extension. Those source files are not listed in the git repository, so should etree even be compiled? Or do I have to link a binary somehow? Sincerely, Corbie

Hi again, I solved this problem myself. I should not have used the git repository but the python package https://pypi.python.org/pypi/lxml/3.4.4 So here comes the next problem: the linker seems to be missing some references: lxml.etree.c
Is this a missing library? And which one? Sincerely, Corbie

On Fri, Nov 20, 2015 at 05:37:42PM +0100, Corvus Corax wrote:
lxml.etree.c is a Cython-generated file from the true source, which is lxml.etree.pyx. lxml releases on PyPI have all the generated files in them, so that users who install from PyPI aren't required to have Cython on installed their machines.
I'd say libxml2. Marius Gedminas -- ...Unix, MS-DOS, and Windows NT (also known as the Good, the Bad, and the Ugly). -- Matt Welsh

Hi Marius, thanks for the answer! In the compiler/linker call the LIBPATH variable is set like this: /LIBPATH:D:\Python\libxslt-1.1.26.win32\lib /LIBPATH:D:\Python\iconv-1.9.2.win32\lib /LIBPATH:D:\Python\zlib-1.2.5\lib /LIBPATH:D:\Python\libxml2-2.7.8.win32\lib /LIBPATH:D:\Programs\Python\libs /LIBPATH:D:\Programs\Python\PC\VC6 libxslt_a.lib libexslt_a.lib libxml2_a.lib iconv_a.lib zlib.lib WS2_32.lib So I can't see why the library still is not found. Do I have to set the variables somehow different? Sincerely, Corbie

On Mon, Nov 16, 2015 at 5:01 PM Corvus Corax <corbie@mailbox.org> wrote:
Extensions should be build with the same compiler that built python, you should probably check if that was indeed VS2013 (I'm unfamiliar with MeVisLab).
Are you building from the git repository? Then you should build with Cython, else you need the source distribution which includes the Cython generated files. HTH, Wietse

Hi, I wrote another mail this week but it seemed to be too confusing. I'm trying to build lxml statically under Windows, but when I do so the script seems to try to build the 'lxml.etree' extension. Those source files are not listed in the git repository, so should etree even be compiled? Or do I have to link a binary somehow? Sincerely, Corbie

Hi again, I solved this problem myself. I should not have used the git repository but the python package https://pypi.python.org/pypi/lxml/3.4.4 So here comes the next problem: the linker seems to be missing some references: lxml.etree.c
Is this a missing library? And which one? Sincerely, Corbie

On Fri, Nov 20, 2015 at 05:37:42PM +0100, Corvus Corax wrote:
lxml.etree.c is a Cython-generated file from the true source, which is lxml.etree.pyx. lxml releases on PyPI have all the generated files in them, so that users who install from PyPI aren't required to have Cython on installed their machines.
I'd say libxml2. Marius Gedminas -- ...Unix, MS-DOS, and Windows NT (also known as the Good, the Bad, and the Ugly). -- Matt Welsh

Hi Marius, thanks for the answer! In the compiler/linker call the LIBPATH variable is set like this: /LIBPATH:D:\Python\libxslt-1.1.26.win32\lib /LIBPATH:D:\Python\iconv-1.9.2.win32\lib /LIBPATH:D:\Python\zlib-1.2.5\lib /LIBPATH:D:\Python\libxml2-2.7.8.win32\lib /LIBPATH:D:\Programs\Python\libs /LIBPATH:D:\Programs\Python\PC\VC6 libxslt_a.lib libexslt_a.lib libxml2_a.lib iconv_a.lib zlib.lib WS2_32.lib So I can't see why the library still is not found. Do I have to set the variables somehow different? Sincerely, Corbie

On Mon, Nov 16, 2015 at 5:01 PM Corvus Corax <corbie@mailbox.org> wrote:
Extensions should be build with the same compiler that built python, you should probably check if that was indeed VS2013 (I'm unfamiliar with MeVisLab).
Are you building from the git repository? Then you should build with Cython, else you need the source distribution which includes the Cython generated files. HTH, Wietse
participants (3)
-
Corvus Corax
-
Marius Gedminas
-
Wietse Jacobs