Displaying 3 results from an estimated 3 matches for "wallm".
Did you mean:
wall
2009 Feb 05
0
[LLVMdev] problems building googletest for 2.5
...ll dynamically test gcc and add
flags, if the flag is supported. I'll leave it up to others to
consider and/or integrate it and consider if /dev/null is portable
enough.
FLAGS := $(shell gcc -Wall -fsyntax-only -xc /dev/null 2>/dev/null &&
echo -Wall)
CFLAGS := $(shell gcc -Wallme -fsyntax-only -xc /dev/null 2>/dev/null
&& echo -Wallme)
all:
@echo flags are $(FLAGS)
@echo flags are $(CFLAGS)
The down side, these execute every time the fragment is read. If
limited to just a few directories, it should be fine, Makefile.common
would hurt.
2009 Feb 05
2
[LLVMdev] problems building googletest for 2.5
Google Test requires these CPP FLAGS "-Wno-missing-field-initializers -
Wno-variadic-macros" in order to not output warnings. However, these
flags are only available with gcc 4.X. We don't want to prevent users
from being able to build with gcc 3.X which is the current situation (http://llvm.org/PR3487
).
I've disabled building Google Test in the 2.5 branch. Hopefully
2009 Feb 05
2
[LLVMdev] problems building googletest for 2.5
...d add
> flags, if the flag is supported. I'll leave it up to others to
> consider and/or integrate it and consider if /dev/null is portable
> enough.
>
> FLAGS := $(shell gcc -Wall -fsyntax-only -xc /dev/null 2>/dev/null &&
> echo -Wall)
> CFLAGS := $(shell gcc -Wallme -fsyntax-only -xc /dev/null 2>/dev/null
> && echo -Wallme)
> all:
> @echo flags are $(FLAGS)
> @echo flags are $(CFLAGS)
>
> The down side, these execute every time the fragment is read. If
> limited to just a few directories, it should be fine, Makefile.common
&...