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

Update minimum MSVC version to 2019 #32614

Merged
merged 1 commit into from
Mar 13, 2023
Merged

Update minimum MSVC version to 2019 #32614

merged 1 commit into from
Mar 13, 2023

Conversation

veblush
Copy link
Contributor

@veblush veblush commented Mar 13, 2023

To be aligned with By google/oss-policies-info#8

@veblush veblush added release notes: yes Indicates if PR needs to be in release notes area/documentation labels Mar 13, 2023
@veblush veblush requested a review from yashykt March 13, 2023 22:03
@veblush veblush enabled auto-merge (squash) March 13, 2023 22:03
@veblush veblush merged commit 0b2609a into grpc:master Mar 13, 2023
@veblush veblush deleted the msvc2017 branch March 13, 2023 22:58
veblush added a commit to veblush/grpc that referenced this pull request Mar 14, 2023
veblush added a commit that referenced this pull request Mar 14, 2023
@copybara-service copybara-service bot added the imported Specifies if the PR has been imported to the internal repository label Mar 14, 2023
XuanWang-Amos pushed a commit to XuanWang-Amos/grpc that referenced this pull request May 1, 2023
davidben added a commit to google/boringssl that referenced this pull request May 8, 2023
This aligns with google/oss-policies-info#8 and
grpc/grpc#32614. VS2019 adds a C11 mode, which
is useful for us, because it means stdalign.h works correctly.

Also bump the minimum Windows SDK to
https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/.
If you have a new MSVC, CMake will enable C11 mode by default. But if
C11 mode is enabled but your Windows SDK is too old, things break.

After this change, the CI will include some redundant configurations.
All the VS2017 configurations will start testing on VS2019, so the
VS2019-specific configurations won't do anything. I'll follow this up
with a change to bump those to VS2022, where we're currently missing
coverage.

Update-Note: BoringSSL now requires VS2019 or later and no longer
supports VS2017. VS2017 has been past its "mainstream end date" for over
a year now, per
https://learn.microsoft.com/en-us/lifecycle/products/visual-studio-2017

Change-Id: I3f359e8ea7c9428ddaa9fcc4ffead2ef903398be
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/59665
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
wanlin31 pushed a commit that referenced this pull request May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation bloat/none imported Specifies if the PR has been imported to the internal repository lang/c++ per-call-memory/neutral per-channel-memory/neutral release notes: yes Indicates if PR needs to be in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants