<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake] Build with Werror in DEVELOPER_MODE (except on the bots)"
href="https://bugs.webkit.org/show_bug.cgi?id=155047#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake] Build with Werror in DEVELOPER_MODE (except on the bots)"
href="https://bugs.webkit.org/show_bug.cgi?id=155047">bug 155047</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=155047#c5">comment #5</a>)
<span class="quote">> Another source of warnings is unused arguments in case function contains #if
> guards. Silencing that would require addition of lots of source lines</span >
You shouldn't see any of these, that's what the UNUSED_PARAM macro is for! Yes, it is often annoying to silence these, but we made a project decision not to disable the warning, though there's a good argument to be made for disabling that warning. (I'm currently planning to do so for DerivedSources only, as that's currently the only place we see any of these, at least on the GTK port.)
But it's irrelevant to whether we should turn warnings into errors, as we don't want preexisting warnings preventing developers from detecting new warnings. Enforcing -Werror in development builds is the best way to ensure the build stays clean and shiny. If you don't want to fix them, you can just use -DENABLE_WERROR=OFF.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>