From 67d042d04f2b6cbe98f4eba2a50ed0d374165cae Mon Sep 17 00:00:00 2001 From: Pierre Rossi Date: Wed, 10 Jul 2013 16:27:48 +0200 Subject: 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 --- qtwebengine.pro | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'qtwebengine.pro') diff --git a/qtwebengine.pro b/qtwebengine.pro index c15cb1919..49108691f 100644 --- a/qtwebengine.pro +++ b/qtwebengine.pro @@ -9,7 +9,11 @@ SUBDIRS = resources \ lib \ process \ build \ # This is where we use the generated qt_generated.gypi and run gyp - examples \ + # Now build the API libraries + lib/quick +qtHaveModule(widgets): SUBDIRS += lib/widgets + +SUBDIRS += examples # Ninja executable location needs to be determined early for extra targets. Should be fetched from cache most of the time anyway. NINJA_EXECUTABLE = $$findNinja() -- cgit v1.2.3