Closed justfalter closed 5 years ago
@justfalter Well it seems the answer is in your question, retarget the solution. Do you have VS? Or just the build?
Otherwise it seems to me you will have to edit the vcxproj to use another toolset that is relevant for 2015 or 2017 which should exist on your machine.
Let me know.
I think the problem is that it uses the wrong VS version 14 and not 17. And that's why it won't work. Try deleting that envar and retry setup.py.
I'm having trouble getting distorm 3.3.8 to build on Windows 10. I've got both Visual Studio 2015 and 2017 installed. When I run
python setup.py build
, I get the output you see in the gist, here.The chief complaint seems to be:
The only VS related variable I have when building is:
Trying to get it to build within a Visual Studio 2017 dev environment doesn't work, either, as it appears that setup.py makes some assumptions about the location of vcvarsall.bat that are not true under VS 2017.