Skip to content
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

Merged
merged 2 commits into from
Apr 1, 2017

Conversation

chalcolith
Copy link
Member

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.

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.
@chalcolith chalcolith added changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge windows labels Apr 1, 2017
@jemc
Copy link
Member

jemc commented Apr 1, 2017

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?

@SeanTAllen
Copy link
Member

Agreed on release

@SeanTAllen SeanTAllen added the triggers release Major issue that when fixed, results in an "emergency" release label Apr 1, 2017
@SeanTAllen SeanTAllen mentioned this pull request Apr 1, 2017
@SeanTAllen SeanTAllen merged commit ff359e9 into ponylang:master Apr 1, 2017
ponylang-main added a commit that referenced this pull request Apr 1, 2017
@SeanTAllen
Copy link
Member

Thanks @kulibali!

@chalcolith chalcolith deleted the vcvars branch April 1, 2017 18:22
@jemc
Copy link
Member

jemc commented Apr 1, 2017

Thank you both!

@shawnye
Copy link

shawnye commented Apr 4, 2017

I am using ponyc-0.12.3 under windows 7 64bit with Visual C++ Build Tools 2015 (Windows 10 SDK not installed)

Error:
ponyc requires a Windows 10 SDK; see https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk
Error:
unable to link: no vcvars

Why should I install gross Windows 10 SDK ?

And no vcvars problem seems not be resolved

@chalcolith
Copy link
Member Author

The Windows 10 SDK is required to use Pony on Windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge triggers release Major issue that when fixed, results in an "emergency" release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants