Suppress build warnings for thirdparty C++ code #264
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
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.
Try to unblock ARM wheel builds for SWE-427.
The Python build includes building some C++ code via Pybind, including several thirdparty libraries. We have strict compile-time checks enabled (
-Wall -Wextra -Werror) which is a good practice, but thirdparty headers often don't conform to all of the checks, especially as newer compiler versions add more of them. To date, we've worked around that by suppressing specific warnings with-Wno-*flags, but that's brittle:It's better to suppress warnings for the thirdparty code, but keep strict checking for our code.