diff options
| author | backer@chromium.org <backer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-10-27 13:49:35 +0000 |
|---|---|---|
| committer | backer@chromium.org <backer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-10-27 13:49:35 +0000 |
| commit | 5c975ed62853fee34c8600cd47138816ee936fe0 (patch) | |
| tree | 646c5a923876ce914b6110c7b71c4e8f5721ad35 /chrome/chrome_tests.gypi | |
| parent | c144060968bce7873e4079bd2293272fe03b520f (diff) | |
| download | chromium_src-5c975ed62853fee34c8600cd47138816ee936fe0.zip chromium_src-5c975ed62853fee34c8600cd47138816ee936fe0.tar.gz chromium_src-5c975ed62853fee34c8600cd47138816ee936fe0.tar.bz2 | |
Fix up compositor mocking.
Two changes:
a) detangle the mock compositor from compositor_test_support
a) pull in compositor when using a mock compositor
Rationale:
a) this target was meant to support using use_webkit_compositor=1 when WK isn't initialized; sometimes we will want to use the mock compositor when WK is initialized
b) we can imagine scenarios where we want to switch between mock and real compositors in the same executable, and it's one less target to update
BUG=101477
TEST=bots stay green
Review URL: http://codereview.chromium.org/8395043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107563 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
| -rw-r--r-- | chrome/chrome_tests.gypi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi index a494626..122d055 100644 --- a/chrome/chrome_tests.gypi +++ b/chrome/chrome_tests.gypi @@ -63,7 +63,7 @@ '../testing/gmock.gyp:gmock', '../testing/gtest.gyp:gtest', '../third_party/leveldatabase/leveldatabase.gyp:leveldatabase', - '../ui/gfx/compositor/compositor.gyp:compositor_test_support', + '../ui/gfx/compositor/compositor.gyp:test_compositor', ], 'export_dependent_settings': [ 'renderer', |