[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now

Roumen Petrov bugtrack at roumenpetrov.info
Fri Jan 23 00:22:28 CET 2009

Luke Kenneth Casson Leighton wrote:
> On Wed, Jan 21, 2009 at 9:13 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>>  ok, so - different from what's being generated by ./configure under
>>> msys under wine or native win32 - what's being generated (libpython 2
>>> . 5 . a and libpython 2 . 5 . dll . a) is more akin to the cygwin
>>> environment.
>>> therefore, there's absolutely no doubt that the two are completely different.
>>> and on that basis, would i be correct in thinking that you _can't_ go
>>> linking or building modules or any python win32 code for one and have
>>> a hope in hell of using it on the other, and that you would _have_ to
>>> rebuild e.g. numpy for use with a mingw32-msys-built version of
>>> python?
>> I can't comment on that, because I don't know what your port does.
>> Does it not produce a .dll containing the majority of Python?
>  no, it contains the minimal necessary amount of python modules,
> exactly like when python is built using cygwin.  actualy, there's a
> few modules that _have_ to be included.
> roumen discovered that you have to have these:
> _functools _functoolsmodule.c    # Tools for working with functions
> and callable objects
> operator operator.c  # operator.add() and similar goodies
> _locale _localemodule.c  # -lintl
> _struct _struct.c
> _subprocess ../PC/_subprocess.c
> _winreg ../PC/_winreg.c

Yes and this is issue in native build - setup.py fail to load :(.
In cross-build where I use python from build system I could produce 
those as modules.

> and i've discovered that when running under wine you have to also have these:
> _weakref _weakref.c
> and also when running unde wine with msvcr80, so far, you have to also
> have these:
> collections collectionsmodule.c
> thread threadmodule.c
> all the rest can be done as .pyd

Actually I didn't spend time to find why MSVC build include so many 
modules as build-ins.


More information about the Python-Dev mailing list