On 12/19/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > At 04:59 PM 12/19/2005 +0100, Daniel Glöckner wrote: > FYI, the shortest path to using MinGW with distutils or setuptools is to > run this script and follow its directions: > > http://mail.python.org/pipermail/python-dev/2004-January/041676.html > > Once you've done that, the version of Python you ran it with will use the > MinGW compiler automatically for all building, with no '-cmingw32' required.
Actually, the referenced script just prints instructions on modifying distutils.cfg, it doesn't do it automatically. > The script should probably be added to Python's "tools" directory, > particularly for Windows. I've just never gotten around to going through > the necessary ceremony to get it in. Probably not any more - see below. > Martin v Loewis has also offered to change Python's Windows distribution a > bit so that the script would be unnecessary, except for setting the [build] > options in distutils.cfg, but I'm not sure if that's happened yet either, > even for Python 2.5. But the script will work for Python 2.3 and up, maybe > even 2.2. As of Python 2.4, this is no longer needed - libpython24.a is shipped with the standard Python Windows installer (and yes, I mean all versions of Python 2.4 - memo to self, must upgrade home PC...) The distutils.cfg change is still needed if you want to make mingw the default - personally, I just use the command line flag --compiler=mingw32. Paul. _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
