path: root/sync.profile
Commit message (Collapse)AuthorAgeFilesLines
* remove dependencies from sync.profileOswald Buddenhagen2016-11-061-16/+0
| | | | | | | the CI obtains them from the qt5 super repo nowadays. Change-Id: If41f7c5306ca739fd3800cec3f680fa72df2a871 Reviewed-by: Jędrzej Nowacki <>
* Add qtlocation dependency to sync.profileAllan Sandfeld Jensen2016-05-301-1/+1
| | | | | | | | | | | Without qtpositioning from qtlocation source module, we have no support for geolocation. Also correct a false dependency on xmlpatterns, and adds a feature report on geolocation at configure time. Change-Id: I7d80b8288631401bf4c8aaa2541327a52910c3e6 Reviewed-by: Michael Brüning <>
* Add a Qt Designer plugin for QWebEngineView.Friedemann Kleint2016-03-311-0/+1
| | | | | | Task-number: QTBUG-52104 Change-Id: Icf8b4eea7fc52498b2ce9a2c04da6a24e8bdb070 Reviewed-by: Kai Koehne <>
* Add public QtWebEngineCore C++ APIAndras Becsi2015-06-081-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch introduces a new public C++ API layer in preparation to make it possible to integrate with lower level Chromium features related mostly to networking operations like accessing and blocking cookies, custom request headers, etc. This API layer can be used both by Qt Widgets and Qt Quick applications with a small C++ core. It should contatain API to access features that usually run on the IO thread to make it possible to perform heavy tasks that would otherwise require costly context switches to the UI thread. Furthermore for these features a QML API does either not make sense, since they are non-UI-related, or a QML API is simply not feasible, because the API is meant for advanced usecases like web browser development (i.e. custom protocol handlers, network traffic interception cookie syncing, etc.). In the long term this layer could also make it possible to reduce code duplication in the widgets and quick layers by moving common parts to the core layer. The new API is built entirely by qmake as a separate static library which is then linked into the QtWebEngineCore library built by gyp and ninja, to prevent the build options passed to Chromium to break the API layer. As a first step this only contains the global headers for core. Change-Id: Iccf8544587cde7c0d9c6abd462e4766bf9ec81ae Reviewed-by: Pierre Rossi <>
* Integrate with WebChannelPierre Rossi2015-02-121-0/+1
| | | | | | | | | | Provide a transport mechanism for WebChannel over chromium IPC and expose WebChannel in our experimental QML API. Co-authored by Milian Wolff. Change-Id: Ia24b1d4ebc8515de677d4849ec33cb55c963918e Reviewed-by: Andras Becsi <>
* Fixup sync.profilePierre Rossi2015-01-151-4/+4
| | | | | | | We shouldn't hardcode to a particular branch there. Change-Id: I9cab855363cfaaa3d8d31879b0c459697a4a6f4c Reviewed-by: Andras Becsi <>
* Depend on Qt 5.4Frederik Gladhorn2014-07-311-4/+4
| | | | | | | | | Several upcomming patches depend on Qt 5.4 (currently the dev branch). In addition Qt WebEngine will be released with Qt 5.4 and the stable branch in Qt is dead. Change-Id: I896c5716c18650b268a13a87b01749d6f3320eeb Reviewed-by: Andras Becsi <>
* Moving sources to src part 2: Adjust paths.Jocelyn Turcotte2013-11-281-3/+4
| | | | | | | | | | | | | | | | | | | NOTE: To build after this you should rerun or run $> git submodule sync $> git submodule update $> git config qtwebengine.chromiumsrcdir src/3rdparty This makes everything build by adjusting paths. Other mixed-in changes: - Rename qtwebengine_src variables in scripts to qtwebengine_root to avoid confusion. - Cleanup the release and debug extra targets that were in This file has also been split into and Change-Id: Ieee9158a65f526b15244eaca59e779b7069d337e Reviewed-by: Zeno Albisser <> Reviewed-by: Pierre Rossi <>
* Add an intermediate Qt5WebEngine module library.Jocelyn Turcotte2013-11-181-0/+1
| | | | | | | | | | | | | | | | | | 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 <>
* Remove unnecessary dependency to qtjsbackend from sync.profileSergio Ahumada2013-10-011-1/+0
| | | | | Change-Id: I240da0d785eaddc81701f36862f1e29d83d686ae Reviewed-by: Andras Becsi <>
* Split out the Widgets and QtQuick integrationPierre Rossi2013-07-311-5/+21
| | | | | | | | | | | | | | | 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 <>
* Add sync.profile for handling dependencies in the Qt CI system.Zeno Albisser2013-07-181-0/+7
Change-Id: I2df4d49ff0e4ed53a38bc666c59a6f4fb943eb46 Reviewed-by: Pierre Rossi <>