-
Notifications
You must be signed in to change notification settings - Fork 12
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
chore: Add support for VS2019 #119
chore: Add support for VS2019 #119
Conversation
Added support for VS2019 and maintained support for VS2017.
Thanks for submitting this pull request! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
VS2019 targets work under VS2019 IDE. VS2017 targets work under VS2017 IDE and VS2019 IDE. The VS2019 targets to not work, which is expected. They give reasonable diagnostics as to why they do not work. This PR is ready for review. |
Appveyor build failure is due to no appveyor config file. I will be submitting a PR to fix this. This is not related to this change. The JSON file is just for IDE config. |
A contributor has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution! |
A contributor has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution! |
Your pull request has been merged and marked as tier 4. It will earn you $20 USD. |
Added support for VS2019 and maintained support for VS2017.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR release a new version?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
develop
branch, not themaster
branchIf adding a new feature, the PR's description includes: