aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar mtklein <mtklein@chromium.org>2014-06-06 08:27:07 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2014-06-06 08:27:07 -0700
commit2e44b51b9a3da1d57328055c4189bf2fa5187e35 (patch)
tree40d0e80a205782e44ee79b976a6f95b2542938f2
parent97724ed4cf5ee29bb6020e50348a84cd2a3bf920 (diff)
Effectively unlimited linking.
Ninja will still cap concurrency with it's default value (from -j), so we just need a big number equal or greater than the number of cores in any machine. BUG=skia: R=borenet@google.com, mtklein@google.com Author: mtklein@chromium.org Review URL: https://codereview.chromium.org/319153002
-rwxr-xr-xgyp_skia5
1 files changed, 5 insertions, 0 deletions
diff --git a/gyp_skia b/gyp_skia
index 040253ec9e..be90916c58 100755
--- a/gyp_skia
+++ b/gyp_skia
@@ -134,6 +134,11 @@ if __name__ == '__main__':
os.environ[ENVVAR_GYP_GENERATOR_FLAGS] = (
gyp_generator_flags + ' msvs_error_on_missing_sources=1')
+ # GYP is very conservative about how many concurrent linker calls it allows,
+ # to fit in RAM. We don't need to be nearly as conservative as Chrome. We'll
+ # just turn that feature off.
+ os.environ['GYP_LINK_CONCURRENCY'] = '9001'
+
print 'Updating projects from gyp files...'
sys.stdout.flush()