-
-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Visual Studio and Microsoft C++ Build Tools detection. #1794
Conversation
Previously `ponyc` would only look for a linker from the version of Visual Studio with which it was compiled, and only looked at one registry key for install information. A recent change (44b2d56) broke support for Visual Build Tools C++ 2015. This change provides registry key and path configuration information for several configurations, regardless of how `ponyc` was compiled for Windows: - Visual Studio 2017 full install - Visual C++ Build Tools 2017 - Visual Studio 2015 full install - Visual C++ Build Tools 2015 The change also removes support for Windows SDKs prior to version 10, as `README.md` now specifies version 10.
Just got a user in IRC who ran into the VS2015 detection issue, so this should probably trigger another patch release (0.12.3). Should we add VS 2017 to the README before merging this? |
Agreed on release |
Thanks @kulibali! |
Thank you both! |
I am using ponyc-0.12.3 under windows 7 64bit with
Why should I install gross And |
The Windows 10 SDK is required to use Pony on Windows. |
Previously
ponyc
would only look for a linker from the version of Visual Studio with which it was compiled, and only looked at one registry key for install information. A recent change (44b2d56) broke support for Visual Build Tools C++ 2015.This change provides registry key and path configuration information for several configurations, regardless of how
ponyc
was compiled for Windows:The change also removes support for Windows SDKs prior to version 10, as
README.md
now specifies version 10.