[issue32292] Building fails on Windows

2017-12-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Ok, I've decided to bite the bullet. I uninstalled VS 2015 and installed VS 2017 Community Edition. Things seem to work now. Thanks for the help! -- resolution: -> fixed stage: -> resolved status: open -> closed

[issue32292] Building fails on Windows

2017-12-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: It's a normal command prompt. Here is the output of "set": https://gist.github.com/pitrou/2baf9950b0ab2f68b39b4973355b2e79 -- ___ Python tracker

[issue32292] Building fails on Windows

2017-12-13 Thread Steve Dower
Steve Dower added the comment: Are you using a normal command prompt or the Visual Studio one? Totally clean environment should work fine these days, but I suspect there's an environment variable affecting something. "set" to show everything that is set, remove any

[issue32292] Building fails on Windows

2017-12-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: > It shouldn't be any different, but what about PCBuild/build.bat? Yes, same thing. -- ___ Python tracker

[issue32292] Building fails on Windows

2017-12-12 Thread Xavier G. Domingo
Change by Xavier G. Domingo : -- nosy: +xgdomingo ___ Python tracker ___ ___

[issue32292] Building fails on Windows

2017-12-12 Thread Steve Dower
Steve Dower added the comment: It shouldn't be any different, but what about PCBuild/build.bat? -- ___ Python tracker ___

[issue32292] Building fails on Windows

2017-12-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Yes, both in x86 and x64. And `tools\buildbot\build.bat` fails regardless of whether I pass `-p x64` or not. -- ___ Python tracker

[issue32292] Building fails on Windows

2017-12-12 Thread Steve Dower
Steve Dower added the comment: Is there one in x86 as well? Perhaps it isn't finding x64 tools properly (I've seen this once or twice in the past with VS 2015, but I think it was fixed at some point) -- ___ Python tracker

[issue32292] Building fails on Windows

2017-12-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Le 13/12/2017 à 01:14, Steve Dower a écrit : > > Strange, that should have been installed. > > Do you see rc.exe anywhere in "C:\Program Files (x86)\Windows Kits\10"? Yes, it's in "C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\x64"

[issue32292] Building fails on Windows

2017-12-12 Thread Steve Dower
Steve Dower added the comment: Strange, that should have been installed. Do you see rc.exe anywhere in "C:\Program Files (x86)\Windows Kits\10"? If not, might need to repair the SDK you just installed. It shouldn't be a separate option from anything else in there.

[issue32292] Building fails on Windows

2017-12-12 Thread STINNER Victor
Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___

[issue32292] Building fails on Windows

2017-12-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Thank you. Though now I get the following issue: "c:\t\cpython\PCbuild\pcbuild.proj" (Build target) (1) -> "c:\t\cpython\PCbuild\pythoncore.vcxproj" (Build target) (2) -> (ResourceCompile target) -> TRACKER :

[issue32292] Building fails on Windows

2017-12-12 Thread Steve Dower
Steve Dower added the comment: I changed the default Windows SDK version at some point, because it was falling back to v8.1 and we really ought to use v10. It auto-detects all the v10 versions, so I'm guessing you haven't got any of them installed right now. The dev

[issue32292] Building fails on Windows

2017-12-12 Thread Antoine Pitrou
New submission from Antoine Pitrou : Sorry if this looks more like a support request. There's probably something wrong in my setup (I do have Visual Studio 2015 installed, though). I am trying to build on Windows using "Tools\buildbot\build.bat -p x64". It worked a few