[issue4954] native build of python win32 using msys under wine.
Luke Kenneth Casson Leighton
report at bugs.python.org
Fri Jan 16 14:42:02 CET 2009
Luke Kenneth Casson Leighton <lkcl at lkcl.net> added the comment:
hi amaury, thanks for responding.
> Is Msys+Mingw32 (running on a regular Windows) an interesting
> configuration to support?
[wine+]msys+mingw32 is used to _build_ python - not depend on it.
[wine+]msys+mingw32 _replaces_ the proprietary build toolchain MSVC.
* in the case of #3871, msys+mingw32 replaces MSVC.
* in the case of #4954, wine+msys+mingw32 replaces MSVC _and_ windows
but in either case, you end up with a complete build of python.exe,
libpython2.5.dll and modules that is perfectly well capable of
running under both wine _and_ native windows...
... WITHOUT requiring, in any way shape or form,
EITHER msys OR mingw32.
in other words, it's a big damn deal.
no more proprietary dependence.
... let me put it this way, martin: if i told richard stallman that
you said that "msys+mingw32 was a minority platform" he'd have
a fit!! :)
> The build tools are similar to the ones used by cygwin, except that the
> C runtime is msvcrt.
yeeees.... sort-of - but if you do s/#ifdef __CYGWIN__/#if defined
(__CYGWIN__) || defined(__MINGW32__) it all goes _horribly_ wrong :)
you actually have to do s/#ifdef _MSC_VER/#if defined(_MSC_VER) ||
defined(__MINGW32__) because _MSC_VER is used alll over the place
to detect and indicate a win32 build (as separate and distinct
from a cygwin build).
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list