On a Friday in 2026, Daniel P. Berrangé via Devel wrote:
From: Daniel P. Berrangé <berrange@redhat.com>
Passing warning flags to the C compiler results in incredibly long command lines, which in turns results in incredibly large CI log files. Our logs are so large that they often exceed the GitLab file limits.
We've cut out the irrelevant cruft from the logs and they're still too large. The only option left is to stop passing so many args to the compiler.
Fortunately it is easy to achieve this with GCC/CLang as when seeing an argument "@somepath" they will treat each line in "somepath" as being an additional compiler argument.
Putting the warning flags in a 'c-warnings.txt' file is fairly easy and a massive win. We don't loose anything from the CI logs
s/loose/lose/
as we print the full set of warning flags at the end of running 'meson'. Meanwhile for interactive builds the flags are visible in the c-warning.txt file in the build directory root.
c-warnings.txt Jano
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> --- meson.build | 114 ++++++++++++++++++++------------------ scripts/meson-warnings.py | 9 +++ 2 files changed, 69 insertions(+), 54 deletions(-) create mode 100644 scripts/meson-warnings.py