Skip to content

Conversation

@MarcelRaad
Copy link
Member

With --enable-warnings, it was not possible to disable warnings via
CFLAGS that got explicitly enabled with that warnings. Now warnings are
not enabled anymore if they are explicitly disabled (or enabled) in
CFLAGS. This works for at least GCC, clang, and TCC as they have
corresponding -Wno- options for every warning.

I'm not fluent with m4, so there might be a better or cleaner way to do that.
Tested with GCC (on Windows and macOS) and clang (on macOS), but TCC should behave the same.

With `--enable-warnings`, it was not possible to disable warnings via
CFLAGS that got explicitly enabled with that warnings. Now warnings are
not enabled anymore if they are explicitly disabled (or enabled) in
CFLAGS. This works for at least GCC, clang, and TCC as they have
corresponding `-Wno-` options for every warning.

Closes
@MarcelRaad
Copy link
Member Author

For some context: what I want to do is enable warnings-as-errors for our macOS CI builds. Most have it disabled at the moment because of a -Wvla warning in a brotli header.

@MarcelRaad MarcelRaad deleted the allow_disabling_warnings branch July 17, 2020 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants