<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#c3">Comment # 3</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:annulen@yandex.ru" title="Konstantin Tokarev <annulen@yandex.ru>"> <span class="fn">Konstantin Tokarev</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=155047#c2">comment #2</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=155047#c1">comment #1</a>)
> > I would rather select a small set of warnings we want to be fatal, and apply
> > -Werror only for them, e.g. -Werror=return-type -Werror=non-virtual-dtor.
> > Later we could extend this list gradually.
>
> TBH I don't see value in this, I would like to enforce either fixing or
> disabling all warnings. (For developers performing development builds.)
>
> We have very few warnings right now, so this shouldn't be any problem.</span >
New version of gcc or clang may introduce new warning by default, resulting in compilation errors in case -Werror is used (e.g., -Winconsistent-missing-override become enabled by -Wall in clang 3.5)</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>