Set clang directory in gyp.

Set clang directory in gyp.

BUG=

[Michael Achenbach, 2014-11-27 11:56:27]

machenbach@chromium.org changed reviewers:
+ jkummerow@chromium.org, jochen@chromium.org

[Michael Achenbach, 2014-11-27 11:56:28]

PTAL

[Michael Achenbach, 2014-11-27 11:58:02]

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

https://codereview.chromium.org/764803002/diff/1/build/standalone.gypi#newcode36
build/standalone.gypi:36: 'make_clang_dir%':
'../third_party/llvm-build/Release+Asserts',
In common.gypi I saw the usages of <(DEPTH) but this goes two dirs backwards.
How is it controlled?

https://codereview.chromium.org/764803002/diff/1/build/standalone.gypi#newcod...
build/standalone.gypi:436: ['clang==1 and ((OS!="mac" and OS!="ios") or
clang_xcode==0) '
This is copied 1:1 from common.gypi

[Jakob Kummerow, 2014-11-27 12:44:14]

lgtm

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

https://codereview.chromium.org/764803002/diff/1/build/standalone.gypi#newcode36
build/standalone.gypi:36: 'make_clang_dir%':
'../third_party/llvm-build/Release+Asserts',
On 2014/11/27 11:58:02, Michael Achenbach wrote:
> In common.gypi I saw the usages of <(DEPTH) but this goes two dirs backwards.
> How is it controlled?

Black magic. I would think that <(DEPTH) should work, but if your testing
indicates otherwise, then ".." is acceptable as well.

[jochen (gone - plz use gerrit), 2014-11-27 15:07:57]

lgtm

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

https://codereview.chromium.org/764803002/diff/1/build/standalone.gypi#newcode36
build/standalone.gypi:36: 'make_clang_dir%':
'../third_party/llvm-build/Release+Asserts',
On 2014/11/27 at 12:44:14, Jakob wrote:
> On 2014/11/27 11:58:02, Michael Achenbach wrote:
> > In common.gypi I saw the usages of <(DEPTH) but this goes two dirs
backwards.
> > How is it controlled?
> 
> Black magic. I would think that <(DEPTH) should work, but if your testing
indicates otherwise, then ".." is acceptable as well.

we shouldn't use DEPTH here, it's only useful for files that are referenced both
from v8 and chromium

[Michael Achenbach, 2014-11-27 16:24:28]

The CQ bit was checked by machenbach@chromium.org

[commit-bot: I haz the power, 2014-11-27 16:25:07]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/764803002/1

[commit-bot: I haz the power, 2014-11-27 16:26:37]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-11-27 16:26:38]

Try jobs failed on following builders:
  v8_mac_rel on tryserver.v8
(http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel/builds/1594)

[Michael Achenbach, 2014-11-27 16:49:32]

The CQ bit was checked by machenbach@chromium.org

[commit-bot: I haz the power, 2014-11-27 16:50:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/764803002/20001

[commit-bot: I haz the power, 2014-11-27 17:18:10]

Committed patchset #2 (id:20001)