diff options
| author | maruel@chromium.org <maruel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-04-04 21:06:46 +0000 |
|---|---|---|
| committer | maruel@chromium.org <maruel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-04-04 21:06:46 +0000 |
| commit | 4df54e8c095bd239b8f7c3786440a4878d2eb509 (patch) | |
| tree | 1b06fa36a4d92cca66ac607adbe45aab342dda47 /base/base.isolate | |
| parent | 73a7a8a02721baddefb25c4a6952760c006f3277 (diff) | |
| download | chromium_src-4df54e8c095bd239b8f7c3786440a4878d2eb509.zip chromium_src-4df54e8c095bd239b8f7c3786440a4878d2eb509.tar.gz chromium_src-4df54e8c095bd239b8f7c3786440a4878d2eb509.tar.bz2 | |
Get rid of all component builds specific .isolate.
The status quo was unmaintainable. These 'component build specific .isolate
files' are superseeded by tools/isolate_driver.py which packages dynamic
libraries automatically.
The new way is much more sane and dynamic, isolate_driver.py is currently very
crude but 'does the job', the expected way to make it work is to read the .ninja
files to extract all the dynamic libraries marked as a dependency to the main
target being executed.
TBR=csharp@chromium.org
BUG=333473
Review URL: https://codereview.chromium.org/226123004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261871 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/base.isolate')
| -rw-r--r-- | base/base.isolate | 43 |
1 files changed, 0 insertions, 43 deletions
diff --git a/base/base.isolate b/base/base.isolate index bfa81fe..442d168 100644 --- a/base/base.isolate +++ b/base/base.isolate @@ -2,50 +2,7 @@ # Use of this source code is governed by a BSD-style license that can be # found in the LICENSE file. { - 'conditions': [ - ['OS=="linux" and component=="shared_library"', { - 'variables': { - 'isolate_dependency_tracked': [ - '<(PRODUCT_DIR)/lib/libbase.so', - '<(PRODUCT_DIR)/lib/libbase_i18n.so', - ], - }, - }], - ['OS=="mac" and component=="shared_library"', { - 'variables': { - 'isolate_dependency_tracked': [ - '<(PRODUCT_DIR)/libbase.dylib', - '<(PRODUCT_DIR)/libbase_i18n.dylib', - ], - }, - }], - ['OS=="win" and component=="shared_library"', { - 'variables': { - 'isolate_dependency_tracked': [ - '<(PRODUCT_DIR)/base.dll', - '<(PRODUCT_DIR)/base_i18n.dll', - ], - }, - }], - ], - # Important note: - # Running: - # 1. GYP_DEFINES=component=shared_library build/gyp_chromium - # 2. ninja -C out/Debug base - # will result with only libbase.so being built. Building base by itself won't - # force the build of icu or nss. This is because base is not usable by itself. - # But on the other hand any test that includes base will be building and - # loading at runtime both icu and nss. So define here what is brought by - # importing base, not what base would load at runtime. - # - # There is no such thing as direct_dependent in .isolate, so it's not the best - # format to describe this kind of thing. But as a user of base.so, the user - # will be importing these other libraries: 'includes': [ - # While the target 'base' doesn't depend on ../build/linux/system.gyp:ssl - # itself, virtually all targets using it has to include - # ../third_party/nss/ssl.gyp:libssl through system.gyp. - '../build/linux/system.isolate', # While the target 'base' doesn't depend on ../third_party/icu/icu.gyp # itself, virtually all targets using it has to include icu. The only # exception is the Windows sandbox (?). |