Phillip J. Eby wrote:
> The Python developers who produce the Windows binaries don't use
> mingw/cygwin, so this would put a maintenance burden on them.
If this were completely automatic (e.g. part of msi.py), I'd happily
add all utilities needed to integrated this into the build process.
For this to happen:
1. Somebody else needs to do the actual work. I.e. write a patch
to msi.py that invokes all the necessary magic, and test that
patch.
2. The patch should avoid manual configuration of the "use cygwin"
case. I.e. it should try to find the cygwin on the path, or in
their standard location, or use any other mechanism available
to locate cygwin. It should produce an error message if cygwin
tools cannot be found, and then proceed without out creating
libpython24.a
Regards,
Martin
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