[Python-Dev] MinGW And The other Py2.4 issue

Paul Moore p.f.moore at gmail.com
Wed Dec 15 10:49:18 CET 2004

On Tue, 14 Dec 2004 23:48:41 +0100, Martin v. Löwis <martin at v.loewis.de> wrote:
> I understand that one still needs to build libpython24.a in order to
> use this process. As I have said, I'd happily ship that file with the
> 2.4.1 MSI, unless the release manager tells me that this would an
> unacceptable new feature, and as long as somebody provides a fully
> automatic build process integrated into msi.py; for that build process,
> it is ok to assume that a cygwin installation is in c:\cygwin.
> So if this would be useful (which I don't know for sure), I still need
> a volunteer to contribute the appropriate magic.

I am willing to work on this, if you wouldn't mind me asking dumb
questions about the build process :-) However, I don't have VS.NET, so
if automation requires integration into the VS project stuff, I can't

For a starter, what steps do you actually take to build a release? I
assume that the first step is to build Python, by clicking on "build"
in VS.NET. Once you have that, is there a single script you run? If
there's a document describing the release process somewhere, feel free
to point me at it.


More information about the Python-Dev mailing list