Add C++20 cppdialect for C++ projects #1460
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update vcxproj.lua * Update dmd.lua * Update ldc.lua * Update gcc.lua * Update test_gcc.lua
starkos
approved these changes
Jun 6, 2020
|
Thanks for taking a look at the CI build. I've been wondering why it was stalled. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR introduces the C++20 standard dialect option to the cppdialect. It sets the corresponding standard flag for MSC, Make, and XCode.
How does this PR change Premake's behavior?
This changes the behavior of MSC's C++17 dialect value from /std:latest to /std:c++17, which is supported in Visual Studio 2019. When running Premake with
cppdialectc++20, c++2a, gnu++20, or gnu++2a, this adds the appropriate standard revision to the compilation.Anything else we should know?
Further down the line, the C++ dialect flags for Xcode should be changed to reflect updates to Apple LLVM's compiler flags. This is out of scope of this PR though.