Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
build-openssl.bat: Refer to VS2017 as VC14.1 instead of VC15 #2189
.. and do the same for build-wolfssl.bat.
Another WIP. @captain-caveman2k as far as I can tell VS2017 is referred to as VC14.1 not VC15. I had some related confusion about this last year and I asked on the MS forums whether it's 14.10 or 14.1 and they said 14.1.
Regarding Enterprise/Professional I haven't tested them yet but I assume they are the same. Basically I added an autodetect so the build script could find the version in order of preference Enterprise -> Professional -> Community
Also there is a Microsoft tool vswhere for more precise Visual Studio location for 2010+.
I believe 14.1 is the version of the compiler and also the toolchain.
The VC in VC15 is kind of short for Visual C++ from the days before Visual Studio. Visual Studio 2017 itself is version 15.
If memory serves me correctly it was known as Dev15 during development and VS "15" during beta - the latest non-preview release is 15.5.6 which I'm running.
So the compiler is version 19.12
The "Platform Toolset" is "Visual Studio 2017 (v141)" (no dots) but that is selectable (in the vcxproj file for msbuild systems, not sure for nmake) going all the way back to at least VC10 with and without XP support.
The Platform is "Visual Studio 15" (mine is 15.5.6, 'cos that has the Spectre switches).
I don't know where that leaves you,
I'd agree with 14.1 because:
Also, in the Apache for Windows world VC15 is the norm:
So, I am -1