A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-December/050430.html below:

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

[Python-Dev] MinGW And The other Py2.4 issue [Python-Dev] MinGW And The other Py2.4 issueDelaney, Timothy C (Timothy) tdelaney at avaya.com
Wed Dec 15 00:50:23 CET 2004
"Martin v. Löwis" wrote:

> Paul Moore wrote:
>> Thanks for your comments. Your support for the viability of building
>> extensions using mingw is important to me, so if you still have any
>> concerns, let me know and I will do my best to address them.
> 
> 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.

I think we should aim to support MSYS as well as Cygwin, but perhaps not for the first version where this goes in.

OTOH, is it really necessary to have either MSYS or Cygwin? MinGW32 works standalone - distutils should be able to just invoke it.

Tim Delaney
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4