Jan Vesely <[email protected]> writes:

> Signed-off-by: Jan Vesely <[email protected]>
> ---
>  src/gallium/state_trackers/clover/Makefile.am | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/src/gallium/state_trackers/clover/Makefile.am 
> b/src/gallium/state_trackers/clover/Makefile.am
> index 4c9d7d9..26ebd3b 100644
> --- a/src/gallium/state_trackers/clover/Makefile.am
> +++ b/src/gallium/state_trackers/clover/Makefile.am
> @@ -1,5 +1,9 @@
>  include Makefile.sources
>  
> +AM_CXXFLAGS = -Werror=switch
> +
> +CXXFLAGS += $(AM_CXXFLAGS)
> +

I'm not much into build systems, but I don't think this is the way
you're supposed to add flags to the compiler command line, because the
user can easily override your definition inadvertently.  AFAIK the usual
idiom is to add AM_CXXFLAGS explicitly to each of the per-target
CXXFLAGS variables.  Once you do that it should be easy to remove some
redundancy between per-target CXXFLAGS (e.g. -std=c++11 and
$(VISIBILITY_CXXFLAGS)).

>  AM_CPPFLAGS = \
>       -I$(top_srcdir)/include \
>       -I$(top_srcdir)/src \
> -- 
> 2.5.5

Attachment: signature.asc
Description: PGP signature

_______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to