Commit fa0f16ec authored by scottmg@chromium.org's avatar scottmg@chromium.org

Only default incremental linking on in shared_library

static_library + incremental explodes due to overly large size when all the
.objs are pulled into the final binary.

BUG=143660


Review URL: https://chromiumcodereview.appspot.com/10825461

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152412 0039d316-1c4b-4281-b951-d872f2087c98
parent 3ff011d4
...@@ -1051,8 +1051,11 @@ ...@@ -1051,8 +1051,11 @@
['component=="shared_library"', { ['component=="shared_library"', {
'win_use_allocator_shim%': 0, 'win_use_allocator_shim%': 0,
}], }],
['"<(GENERATOR)"=="ninja"', { ['component=="shared_library" and "<(GENERATOR)"=="ninja"', {
# Only enabled by default for ninja because it's buggy in VS. # Only enabled by default for ninja because it's buggy in VS.
# Not enabled for component=static_library because some targets
# are too large and the toolchain fails due to the size of the
# .obj files.
'incremental_chrome_dll%': 1, 'incremental_chrome_dll%': 1,
}], }],
# Whether to use multiple cores to compile with visual studio. This is # Whether to use multiple cores to compile with visual studio. This is
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment