Add ASAN option to stand-alone gyp config.

Add ASAN option to stand-alone gyp config.

BUG=
R=jkummerow@chromium.org, jochen@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=19888

[Michael Achenbach, 2014-03-12 16:36:40]

PTAL - this seems to not have the desired effect yet. I tried: 

export CXX="$CLANG/clang++"
export LINK="$CLANG/clang++"
export ASAN_SYMBOLIZER_PATH="$CLANG/llvm-symbolizer"
GYPFLAGS="-Dasan=1"  make -j32 ia32.release.check

and I was hoping to get the same effect as with:

export LINK="$CLANG/clang++ -fsanitize=address"
export CXX="$CLANG/clang++ -fsanitize=address"
export ASAN_SYMBOLIZER_PATH="$CLANG/llvm-symbolizer"
make -j32 ia32.release.check

[jochen (gone - plz use gerrit), 2014-03-13 08:25:27]

https://codereview.chromium.org/196943004/diff/1/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/196943004/diff/1/build/standalone.gypi#newcod...
build/standalone.gypi:174: 'target_conditions': [
why only for the target toolset?

[Michael Achenbach, 2014-03-13 09:19:06]

Patch 2 works when running:

export CC="$CLANG/clang"
export CXX="$CLANG/clang++"
export CC_host="$CLANG/clang"
export CXX_host="$CLANG/clang++"
export LINK="$CLANG/clang++"
export ASAN_SYMBOLIZER_PATH="$CLANG/llvm-symbolizer"
GYPFLAGS="-Dasan=1"  make -j32 ia32.release.check

But is there too much done? My original code was inspired by a similar config
for chromium:
https://code.google.com/p/chromium/codesearch#chromium/src/build/common.gypi&...

[Michael Achenbach, 2014-03-13 10:09:45]

PTAL at patch 3. This works with:

export CXX="$CLANG/clang++"
export CXX_host="$CLANG/clang++"
export LINK="$CLANG/clang++"
export ASAN_SYMBOLIZER_PATH="$CLANG/llvm-symbolizer"
GYPFLAGS="-Dasan=1"  make -j32 ia32.release.check

This should be enough to make it work on the bots.

[jochen (gone - plz use gerrit), 2014-03-13 10:12:45]

https://codereview.chromium.org/196943004/diff/40001/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/196943004/diff/40001/build/standalone.gypi#ne...
build/standalone.gypi:174: 'target_defaults': {
does it also work if you use conditions: asan==1: target_conditions:
toolset==_target?

[Michael Achenbach, 2014-03-13 10:18:51]

It seems to work also like this:

    ['asan==1', {
      'target_defaults': {
        'target_conditions': [
          [ '_toolset=="target"', {
            'cflags_cc+': ...
          }],
        ],
      }
    }],

But then we don't have coverage for makesnapshot anymore, right?

[jochen (gone - plz use gerrit), 2014-03-13 10:27:37]

On 2014/03/13 10:18:51, Michael Achenbach wrote:
> It seems to work also like this:
> 
>     ['asan==1', {
>       'target_defaults': {
>         'target_conditions': [
>           [ '_toolset=="target"', {
>             'cflags_cc+': ...
>           }],
>         ],
>       }
>     }],
> 
> But then we don't have coverage for makesnapshot anymore, right?

right. I just thought because you wanted to match the chromium version

either why

lgtm

[Jakob Kummerow, 2014-03-13 10:28:30]

LGTM too.

[Michael Achenbach, 2014-03-13 10:37:07]

Committed patchset #3 manually as r19888 (presubmit successful).