Handle disablewarnings for visual studio with clang
#2529
Merged
Conversation
This file contains hidden or 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
samsinsane
approved these changes
Oct 30, 2025
Jarod42
added a commit
to Jarod42/premake-core
that referenced
this pull request
Nov 6, 2025
…tudio with clang (premake#2529)
Jarod42
added a commit
to Jarod42/premake-core
that referenced
this pull request
Nov 6, 2025
…tudio with clang (premake#2529)
Jarod42
added a commit
to Jarod42/premake-core
that referenced
this pull request
Nov 6, 2025
…tudio with clang (premake#2529)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
close #2522
How does this PR change Premake's behavior?
visual project with clang now handle
disablewarningsAnything else we should know?
Also tested on my sample-test-project
Did you check all the boxes?
closes #XXXXin comment to auto-close issue when PR is merged)