Split out the Widgets and QtQuick integration

This is the first step to making proper Qt Modules out of QtWebEngine.
The Widgets integration becomes a proper C++ Qt Module while we make
the QtQuick side a QML plugin for now (could probably be promoted if
the need arises).

Code-wise, this means the introduction of a WebContentsAdapterClient
interface that is subclassed by the private implementation of our API
classes for delegation of things that are UI specific. Functionality
from WebContents and the like is exposed via the WebContentsAdapter.

Change-Id: I4ca3395b9fe8502a24e36002cfd5af44067bb6e8
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

1 files changed, 21 insertions, 5 deletions

diff --git a/sync.profile b/sync.profile
index 24a6cba89..da4707588 100644
--- a/sync.profile
+++ b/sync.profile
@@ -1,7 +1,23 @@
-# A list of Qt dependencies to build QtWebEngine.
+%modules = ( # path to module name map
+    "QtWebEngineWidgets" => "$basedir/lib/widgets",
+);
+%moduleheaders = ( # restrict the module headers to those found in relative path
+    "QtWebEngineWidgets" => "Api",
+);
+%classnames = (
+);
+
+# Module dependencies.
+# Every module that is required to build this module should have one entry.
+# Each of the module version specifiers can take one of the following values:
+#   - A specific Git revision.
+#   - any git symbolic ref resolvable from the module's repository (e.g. "refs/heads/master" to track master branch)
+#
 %dependencies = (
-        "qtbase" => "refs/heads/stable",
-        "qtxmlpatterns" => "refs/heads/stable",
-        "qtjsbackend" => "refs/heads/stable",
-        "qtdeclartive" => "refs/heads/stable",
+    "qtbase" => "refs/heads/stable",
+    "qtdeclarative" => "refs/heads/stable",
+    "qtjsbackend" => "refs/heads/stable",
+    "qtxmlpatterns" => "refs/heads/stable",
+# FIXME: take examples out into their own module to avoid a potential circular dependency later ?
+    "qtquickcontrols" => "refs/heads/stable",
 );