Luke Kenneth Casson Leighton <l...@lkcl.net> added the comment: > The current patch makes too many changes in core distutils functions; > it cannot be accepted in this form. I'm sure that most of the needed > changes can be made in a subclass of the present Mingw32CCompiler.
that's what i did when creating the _other_ (yet another) mingw32 patch - however _some_ minimal changes to core distutils _are_ unfortunately required. and to sys.py and os.py - this is, after all, a new platform! it starts off with "sys.platform == 'mingw32'", requiring detection of gcc compiler type BUT and os type of win32, and goes from there. right now, detection logic is: * "if gcc on win32 platform, platform MUST be cygwin" * "if msvc compiler, platform MUST be win32" both of which are... well... wrong! :) so, i found that it was necessary to start in os.py and sys.py, create a platform-type "mingw32" and _then_ it was easy to do a MingW32Compiler etc. with (mostly) additions not modifications to distutils, but _necessary_ to add in detection of the type. if distutils was designed to do "exec import distutils.compiler.%s as compiler" % sys.platform and go from there then this would be an entirely non-issue: no modifications to distutils would be required, just a completely separate module containing the new compiler... ... but distutils isn't designed that way, is it? :) l. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3871> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
