[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
Luke Kenneth Casson Leighton
lkcl at lkcl.net
Thu Jan 22 11:57:07 CET 2009
On Thu, Jan 22, 2009 at 9:18 AM, Amaury Forgeot d'Arc
<amauryfa at gmail.com> wrote:
>> or, is the .pyd loading a bit cleverer (or perhaps a bit less
>> cleverer) than i'm expecting it to be?
> On Windows, you must turn on the --enable_shared option if you want to
> build extension modules.
> You could take the cygwin build as an example, see what's done in
amaury, thank you for mentioning that - yes, as it turns out, all of
the mingw ports (dan, roumen etc) do pretty much exactly this. also
it turns out that on mingw, if you _don't_ disable shared (i.e. if you
try to build a static library) mingw32 gcc runtime utils .16, .17
_and_ .19 all segfault or have runtime assertions when creating the
archives!! either ar.exe or ranlib.exe choke themselves to death.
which is greaaat. so, i've had to set the variable which specifies the
libpython2.5.a static library to "" in order to stop it from being
it would be helpful if there was a --enable-static=yes/no configure
option, but there isn't one.
leaving that aside, you understand therefore that dan, roumen and i
have all managed to achieve building of .pyd extension modules.
so, the question i am asking is: would it be reasonable to expect
mingw-compiled .pyd modules to work with a proprietary-compiled msvc
python.exe, and vice-versa?
More information about the Python-Dev