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

"Martin v. Löwis" martin at v.loewis.de
Wed Jan 21 22:13:26 CET 2009

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? And is that not called python25.dll?

Regards, Martin

More information about the Python-Dev mailing list