summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRoland Kaufmann <rka081+numpy@uib.no>2016-12-12 09:40:08 +0100
committerRoland Kaufmann <roland.kaufmann@uni.no>2016-12-12 12:44:25 +0100
commit21eeac2ebffd88461ae95e9d0dd487b12fab993e (patch)
treeaa0ff9be4195c59520ed788b5cae1d5ad7c93d3f /doc
parent9a4691fd4e66a29441c5e5fd582a2c7e1eedb557 (diff)
downloadnumpy-21eeac2ebffd88461ae95e9d0dd487b12fab993e.tar.gz
DOC: MinGW is partially supported, with caveats
MinGW can be used to build extensions, but will most likely fail for extensions that uses the runtime extensively. This is just a band-aid until Mingwpy is fully functional for calculation code written in Fortran.
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.13.0-notes.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/release/1.13.0-notes.rst b/doc/release/1.13.0-notes.rst
index d41b06c37..eed3f7266 100644
--- a/doc/release/1.13.0-notes.rst
+++ b/doc/release/1.13.0-notes.rst
@@ -74,6 +74,18 @@ behaviour is recovered if ``axis=None`` (default).
Improvements
============
+Partial support for 64-bit f2py extensions with MinGW
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Extensions that incorporate Fortran libraries can now be built using the free
+MinGW_ toolset, also under Python 3.5. This works best for extensions that only
+do calculations and uses the runtime modestly (reading and writing from files,
+for instance). Note that this does not remove the need for Mingwpy; if you make
+extensive use of the runtime, you will most likely run into issues_. Instead,
+it should be regarded as a band-aid until Mingwpy is fully functional.
+
+.. _MinGW: https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/6.2.0/threads-win32/seh/
+
+.. _issues: https://mingwpy.github.io/issues.html
Changes
=======