Hi,
basically the toolchain was created with a local fork of the "mingw-builds"
build process along with some addons and patches. It is NOT a mingw-w64
fork. BTW: there are numerous mingw-w64 based toolchains out there, most of
them build without any information about the build process and patches they
used.
As long as the "mingw-builds" maintainers continue working on their
project, maintaining usuable toolchain for Python development on Windows
should be feasible.
More details are given here:
http://article.gmane.org/gmane.comp.python.numeric.general/57446
Regards
Carl
2014-04-25 7:57 GMT+02:00 Sturla Molden
Matthew Brett
wrote: Thanks to Cark Kleffner's toolchain and some help from Clint Whaley (main author of ATLAS), I've built 64-bit windows numpy and scipy wheels for testing.
Thanks for your great effort to solve this mess.
By Murphy's law, I do not have access to a Windows computer on which to test now. :-(
This approach worries me a bit though: Will we have to maintain a fork of MinGW-w64 for building NumPy and SciPy? Should this toolset be distributed along with NumPy and SciPy on Windows? I presume it is needed to build C and Cython extensions?
On the positive side: Does this mean we finally can use gfortran on Windows? And if so, can we use Fortran versions beyond Fortran 77 in SciPy now? Or is Mac OS X a blocker?
Sturla
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion