New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building extensions with MSVC 2015 Express fails #70037
Comments
MSVC 2015 Express doesn't include the 64-bit compiler [1], and this causes distutils to fail to load proper compiler settings when using a 64-bit machine to compile extensions for 64-bit python. _msvccompiler.py tries to call "vcvarsall.bat amd64", but the VC\bin\amd64 directory contains only one file "vcmeta.dll". [1] https://msdn.microsoft.com/en-us/library/hs24szh9(v=vs.140).aspx |
I'm inclined to close this as 'not a bug'. There's not much we can do about that (if you want 64 bit extensions, you need a 64 bit compiler), and 2015 Community Edition does include the 64 bit compiler (if you select it). I'm not sure if there's anything to be done in distutils to handle things more gracefully. |
There is: we can fall back on the cross compilers if the native ones are not there. Not a huge change, and safe enough. |
New changeset fc117df27143 by Steve Dower in branch '3.5': New changeset 37dc870175be by Steve Dower in branch 'default': |
For anyone interested, there's no issue with using the cross compilers even on a 64-bit system. The same code will be generated, the only difference is that the native 64-bit compilers can keep more in memory than the 32-bit cross compilers. For most Python extensions this won't matter (it matters for building huge projects like an operating system). |
test_distutils is now failing on "AMD64 Windows7 SP1 3.x" buildbot: please see issue bpo-26207. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: