diff options
| author | dpranke <dpranke@chromium.org> | 2015-11-13 11:17:37 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-11-13 19:18:29 +0000 |
| commit | d434bf3f1b28416a88604325372a01b908c099c0 (patch) | |
| tree | f5f8da2eecf13547f4e1ddde90a48353915565d9 /build | |
| parent | ecaad3ed68ce40ebace432938af511c51660255c (diff) | |
| download | chromium_src-d434bf3f1b28416a88604325372a01b908c099c0.zip chromium_src-d434bf3f1b28416a88604325372a01b908c099c0.tar.gz chromium_src-d434bf3f1b28416a88604325372a01b908c099c0.tar.bz2 | |
Allow goma to work w/ NaCl toolchains in GN build.
This change allows the default logic for goma to work
for NaCl (which appears to work fine, at least in local
testing, and it looks like build_nexe.py supports goma
these days as well).
Let's enable this and see what happens; if this doesn't
work, then we need to figure out a way to set a
per-toolchain limit on concurrent compiles like there
is for concurrent_links , and figure out how to make
that get set appropriately for nacl differently from
cc.
R=mcgrathr@chromium.org
BUG=555123
Review URL: https://codereview.chromium.org/1437303002
Cr-Commit-Position: refs/heads/master@{#359595}
Diffstat (limited to 'build')
| -rw-r--r-- | build/toolchain/nacl_toolchain.gni | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/build/toolchain/nacl_toolchain.gni b/build/toolchain/nacl_toolchain.gni index fa79038..4864fd7 100644 --- a/build/toolchain/nacl_toolchain.gni +++ b/build/toolchain/nacl_toolchain.gni @@ -51,7 +51,6 @@ template("nacl_toolchain") { is_component_build = false clear_sanitizers = true use_ccache = false - use_goma = false rebuild_define = "NACL_TC_REV=" + invoker.toolchain_revision } |