Use the WebTestProxy for layout tests in content_shell

content/content_renderer.gypi

Index: content/content_renderer.gypi
diff --git a/content/content_renderer.gypi b/content/content_renderer.gypi
index 269df95e06e589c9dbe2f652ae1e4fb94523b658..790274b215c92f46fe153774364f1185a15ec094 100644
--- a/content/content_renderer.gypi
+++ b/content/content_renderer.gypi
@@ -270,6 +270,15 @@
     'renderer/websharedworkerrepository_impl.h',
   ],
   'conditions': [
+    ['component=="shared_library" and OS!="ios"', {
+      'sources': [
+        'public/test/content_layouttest_support.h',
+        'test/content_layouttest_support.cc',

[jam, 2012/11/08 20:37:06]

why is this dependency there on shared builds?

[jochen (gone - plz use gerrit), 2012/11/08 20:41:08]

The alternative is to content_export RenderViewImpl and all of its base classes.
Given that shared builds are a development-only thing that seemed like the
better alternative.

In WebKit, we do the same with the webkit_test_support target. In a shared
library build, we just build the test stuff into the webkit.dll

[jam, 2012/11/08 20:49:24]

would this only be RenderViewImpl and RenderWidget?

even if we have to export the other interfaces, there aren't that many
we put in CONTENT_EXPORT all over the code already to support dev-only shared
builds, so not sure why this would be different? I ask because there's a price
for this complication of the gypi files as well.

+      ],
+      'dependencies': [
+        '<(webkit_src_dir)/Tools/DumpRenderTree/DumpRenderTree.gyp/DumpRenderTree.gyp:TestRunner',
+      ],
+    }],
     ['notifications==0', {
       'sources!': [
         'renderer/notification_provider.cc',