SCons: Fix MSVC bypassing disabled warnings #100185
Merged
+56
−68
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.
Merging #94321 exposed a bug in our SCons setup on MSVC: some warnings persist even when they should've been disabled via
/w
. Technically, this is more of an MSVC bug, but this was fixed by implementing these two changes:disable_warnings
are the flags that change the overall warning scopewarning=no
is passed, ensure that/wd4267
is explicitly appended alongside/w
This includes a few other changes that were integrated while getting to the bottom of this, as they were tangentally related:
csg
module now correctly rebuilds itself if third-party libraries changedisable_warnings
functions to their main equivalent