[haiku-commits] Re: haiku: hrev46660 - build/jam src/system/libroot/posix/glibc/stdio-common
- From: Jonathan Schleifer <js-haiku-commits@xxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 14 Jan 2014 13:14:45 +0100
Am 14.01.2014 um 11:12 schrieb Ingo Weinhold <ingo_weinhold@xxxxxx>:
> 1. Add an optional parameter (a build feature specification) to EnableWerror
> that allows us to disable the warnings for clang.
>
> 2. Disable -Werror for clang for every component.
>
> 3. (Over time) Component by component fix all clang warnings and enable
> -Werror.
>
> This is basically the same approach we have used for introducing -Werror in
> the first place. As you can see, it has allowed us to clear the (gcc)
> warnings for a substantial part of the code base already. So it has been
> proven to work for us.
>
> As I and again Axel have tried to explain, iteratively enabling -Werror for
> warning types for the whole code base, as you suggest, is very likely not
> going to work for us.
Ok, I will do it like this then. I still don't think it's a good idea, as every
new Clang release adds a ton of new warnings, but ok. It doesn't matter that
much anyway, as I think there is currently not a single component that builds
without warnings when using Clang.
So the patch should actually change all places where EnableWerror is called? Or
is there something like default values for targets, so that I can disable it
for Clang by default?
--
Jonathan
Other related posts:
