➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients db3l, jeremy.kloth, jkloth, miss-islington, pablogsal, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-12-11.00:13:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544487203.07.0.788709270274.issue35433@psf.upfronthosting.co.za>
In-reply-to
Content 
So before the change, the 16299 SDK wasn't being detected either, but perhaps the 10240 one was? That had some known issues in the debug UCRT, which is why the version gets printed out towards the end of the build.

The only thing I can think of would be the WindowsTargetPlatformVersion setting, which is new. It may be that it is used differently on different MSBuild versions (which roughly match to VS versions) by the built-in target files.

Are you able to run "MSBuild pythoncore.vcxproj /t:ShowVersionInfo /flp:v=diag" and upload the MSBuild.log file (or email it to me)?
History
Date User Action Args
2018-12-11 00:13:23steve.dowersetrecipients: + steve.dower, paul.moore, db3l, vstinner, tim.golden, jkloth, jeremy.kloth, zach.ware, pablogsal, miss-islington
2018-12-11 00:13:23steve.dowersetmessageid: <1544487203.07.0.788709270274.issue35433@psf.upfronthosting.co.za>
2018-12-11 00:13:23steve.dowerlinkissue35433 messages
2018-12-11 00:13:22steve.dowercreate