summaryrefslogtreecommitdiffstats
path: root/qtwebengine.gypi
diff options
context:
space:
mode:
authorAndras Becsi <andras.becsi@digia.com>2013-07-05 18:34:45 +0200
committerSimon Hausmann <simon.hausmann@digia.com>2013-07-09 13:45:41 +0200
commit1daab3653e56469868656b32fa87b7f9585ec577 (patch)
tree10a9cfe812347ed2582a7f68a7ffdc27726e81c0 /qtwebengine.gypi
parenta912e57e189847509efd75d8a4563ad8c7aa1079 (diff)
Get rid of the need to export content::GetContentClient()
ContentBrowserClientQt is a singleton which makes it possible to access it from WebContentsViewQt and removes the need for patching chromium. This is similar to how ShellContentBrowserClient is managed in the content shell. Change-Id: I67f35520935388888c7230806ad543a58b3211c3 Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
Diffstat (limited to 'qtwebengine.gypi')
-rw-r--r--qtwebengine.gypi2
1 files changed, 0 insertions, 2 deletions
diff --git a/qtwebengine.gypi b/qtwebengine.gypi
index a518d46fd..5d793b0ea 100644
--- a/qtwebengine.gypi
+++ b/qtwebengine.gypi
@@ -11,8 +11,6 @@
}],
],
},
-# Needed to get access to content::GetContentClient()
- 'defines': ['CONTENT_IMPLEMENTATION'],
'dependencies': [
'<(chromium_src_dir)/content/content.gyp:content',
'<(chromium_src_dir)/content/content.gyp:content_app',