3 ms·

roger - 1st a big thank you for the wonderful service you provide. I assume you are aware of this: https://blogs.msdn.microsoft.com/vcblog/2015/11/02/announci

by smortaz 11y ago

roger - 1st a big thank you for the wonderful service you provide. I assume you are aware of this: https://blogs.msdn.microsoft.com/vcblog/2015/11/02/announcing-visual-c-build-tools-2015-standalone-c-tools-for-build-environments/ https://blogs.msdn.microsoft.com/vcblog/2015/11/02/announcin... The python team actually pushed for this unbundling. Which other versions do you need? I can take than info back to the VC++ team. There's also this for VM's: https://blogs.msdn.microsoft.com/visualstudio/2015/01/08/azure-virtual-machine-images-for-visual-studio/ https://blogs.msdn.microsoft.com/visualstudio/2015/01/08/azu... Thanks.

rogerbinns 11y ago
Those are the "most recent version" I mentioned. The Visual Studio versions and Python adoption are out of sync. To build for the versions of Python I do, VS 2008, 2010, and whatever Python 3.5 needs. Note that the free versions excluded 64 bit compilation so the resource kit had to be used. Here is my setup doc https://github.com/rogerbinns/apsw/wiki/Setting-up-a-Windows-7-64-bit-build-environment https://github.com/rogerbinns/apsw/wiki/Setting-up-a-Windows...
- smortaz 11y ago
  Thanks rogerbinns - Understood, just wanted to make sure you were aware & it looks like you are :). I've pinged the VC++ team and will report back. BTW we've setup the alias pythonbuildtools at microsoft.com where folks like you that are building pkgs can speak to the Python+VC++ team members. I recommended send your request there as well. Cheers.