summaryrefslogtreecommitdiffstats
path: root/lib/quick/quick.pro
Commit message (Collapse)AuthorAgeFilesLines
* Add an intermediate Qt5WebEngine module library.Jocelyn Turcotte2013-11-181-6/+8
| | | | | | | | | | | | | | | | | | Make the WebEngine QtQuick plubin library a library only that fetches the API privatly from the official module. This will allow an experimental plugin library to also have access to the API classes, which it currently can't since the plugins aren't deployed the same way as module to <prefix>/lib. The module currently only export classes privately but the plan is to make this library the official linking point of entry for applications along with the Qt5WebEngineWidgets module. The WebEngineCore library could eventyally be merged into this module library if we can get gyp to play well with qmake. Change-Id: I5edb60b412e213b59f791a7b8df9f28c295502de Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Remove the need for application to set an RPATH.Jocelyn Turcotte2013-11-181-1/+1
| | | | | | | | | | | | | The WebEngineWidgets module and the WebEngine QtQuick plugin libraries already have the RPATH set properly in their headers and the application won't need to link any symbol directly to the Core library. Remove the RPATH directive for examples and tests and fix the build issue by making sure that the link directive isn't passed to dependencies through the prl or pkgconfig file. Change-Id: Id1f5efb8c9823613e804e8e6356d711d561d72ec Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* We should still be able to build with Qt 5.1 for the time being.Andras Becsi2013-10-071-0/+3
| | | | | | | | | | Also remove 3rdparty_upstream from from submodules, accidentally added in https://codereview.qt-project.org/#change,67241 This fixes init-repository.py. Change-Id: I08c095e4830581156efc3f069e00e733dda1ffd8 Reviewed-by: Adam Kallai <kadam@inf.u-szeged.hu> Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Remove v8-private private dependencyPierre Rossi2013-10-041-1/+1
| | | | | | | Long live the new v4 (formerly known as v4vm)! :) Change-Id: I9648e43276abb332b270a7c788a4bbff7334b919 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Use QObject::d_ptr for public API classesJocelyn Turcotte2013-08-201-0/+1
| | | | | | | | | | | This follows the model used by the rest of Qt, potentially avoiding binary compatibility issues. The compromise is that we now depend on core-private, thus forcing us to follow Qt's release cycle. Change-Id: Ib2df51071fc35935ac99edf7b9c5562949cb43e2 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Change "Contents" to "Engine" in API class names.Jocelyn Turcotte2013-08-191-3/+3
| | | | | Change-Id: I58d83f4f33728f92e4bf13b6be30b15528fdd033 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Split out the Widgets and QtQuick integrationPierre Rossi2013-07-311-0/+28
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>