Set cc_flags for cmake build on Mac

Set cc_flags for cmake build on Mac
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1618313003

[bsalomon, 2016-01-22 15:37:15]

Description was changed from

==========
Set cc_flags for cmake build on Mac
==========

to

==========
Set cc_flags for cmake build on Mac
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...
==========

[bsalomon, 2016-01-22 16:03:54]

bsalomon@google.com changed reviewers:
+ herb@google.com, mtklein@google.com

[bsalomon, 2016-01-22 16:03:54]

Not intended to land.

Do you guys have some tricks for making CLion/cmake builds work on Mac? This
gets me past compile errors but then I get linker errors because of SDKROOT in
the path to frameworks.

[mtklein, 2016-01-22 16:14:18]

https://codereview.chromium.org/1618313003/diff/1/gyp/common_conditions.gypi
File gyp/common_conditions.gypi (right):

https://codereview.chromium.org/1618313003/diff/1/gyp/common_conditions.gypi#...
gyp/common_conditions.gypi:533: 'WARNING_CFLAGS': [
One trick I've often considered is that any cflags can go in here, not just
warning flags.

We could pile most things into a variable that we then expand into
WARNING_CFLAGS and 'cflags', removing most of these CLANG_ and GCC_ one-off
settings for the version in comments on the right.

That doesn't help C++-specific flags, like -std=c++11 and -fnortti. 
WARNING_CFLAGS is used for C and C++ code alike.

[mtklein, 2016-01-22 16:14:55]

On 2016/01/22 16:03:54, bsalomon wrote:
> Not intended to land.
> 
> Do you guys have some tricks for making CLion/cmake builds work on Mac? This
> gets me past compile errors but then I get linker errors because of SDKROOT in
> the path to frameworks.

FWIW, I don't use CLion or cmake-via-GYP on a Mac, or anywhere.

[bsalomon, 2016-01-22 16:25:34]

https://codereview.chromium.org/1618313003/diff/1/gyp/common_conditions.gypi
File gyp/common_conditions.gypi (right):

https://codereview.chromium.org/1618313003/diff/1/gyp/common_conditions.gypi#...
gyp/common_conditions.gypi:533: 'WARNING_CFLAGS': [
On 2016/01/22 16:14:18, mtklein wrote:
> One trick I've often considered is that any cflags can go in here, not just
> warning flags.
> 
> We could pile most things into a variable that we then expand into
> WARNING_CFLAGS and 'cflags', removing most of these CLANG_ and GCC_ one-off
> settings for the version in comments on the right.
> 
> That doesn't help C++-specific flags, like -std=c++11 and -fnortti. 
> WARNING_CFLAGS is used for C and C++ code alike.

With Herb's change to gyp --std=c++11 is applied to all the cmake C++ compiles,
but these other flags are not (WARNING_CFLAGS and CLANG_/GCC_ settings alike).
So something like that seems like a step forward.