Disable C compiler warnings entirely #555
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
|
@serebit Now it triggers the following:
So still need those it seems |
JoshStrobl
pushed a commit
that referenced
this pull request
Jun 21, 2024
* Disable C compiler warnings entirely * Add back existing warning disablement
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.
Description
In Meson 1.4.0, warnings for Vala-transpiled C code were unhidden, which causes the Budgie build to turn into unreadable logspam due to the absolutely abysmal C code generated by Vala. This PR restores the prior behavior by disabling all warnings for C code.
Let it be known that I didn't want to have to do this and would have fixed the code myself. If I could have.
Submitter Checklist
git rebase -i(if needed)