Issue
Trying to install PySide and I am getting this error:
running build
Python architecture is 64bit
nmake not found. Trying to initialize the MSVC env...
Searching MSVC compiler version 10.0
error: Failed to find the MSVC compiler version 10.0 on your system.
I have minGW, QT 4.8 vs 2010 and mingw versions, Cmake.
Now I have a feeling that something is missing from my PATH, but I'm not sure where and what should it point. My current PATH:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Python34\;C:\Python34\Scripts;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Windows\System32;C:\Program Files (x86)\CMake 2.8\bin
Any suggestions?
Solution
According to your comment you have the redistributable package for VS2010. This installs the runtime components that are needed for applications built with VS2010.
However, the error message you show indicates that the module you are trying to install requires the C++ compiler from VS2010. Presumably that's because you are attempting to install from source.
Compounding your misery you have 64 bit Python which requires a 64 bit version of the C++ compiler. Such a thing does exist, but it's not available easily for free. The free Express versions of VS have moved on to VS2013 now. It's hard to come by a download for the 2010 Express. And in any case, that never shipped with a 64 bit compiler.
You could obtain the 64 bit VS2010 compiler from the Windows SDK of the day, and that's how I personally obtained it. In fact I closely guard the installer for that version of the SDK so that I will always have access to the 64 bit VS2010.
Frankly I think you'd be best off installing a binary version rather than from source. The best source of these is the wonderful site maintained by Christoph Gohlke. Although he's not yet updated the PySide downloads with one for Python 3.4 so in this case you'll be stymied.
I also note that the PySide site has a good set of Windows binary downloads. But again, not for Python 3.4. Perhaps you are just a little bit too close to the bleeding edge of progress for your own good. You might be well advised to back off to Python 3.3 until all the third party developers can catch up. After all, Python 3.4 only hit the tubes a fortnight ago.
Answered By - David Heffernan
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.