-
Qt by Nokia authored
This is the beginning of revision history for this module. If you want to look at revision history older than this, please refer to the Qt Git wiki for how to use Git history grafting. At the time of writing, this wiki is located here: http://qt.gitorious.org/qt/pages/GitIntroductionWithQt If you have already performed the grafting and you don't see any history beyond this commit, try running "git log" with the "--follow" argument. Branched from the monolithic repo, Qt master branch, at commit 896db169ea224deb96c59ce8af800d019de63f12
50123887
- QtWebEngine - Combining the power of Chromium and Qt
- I. Getting the Code
- 1) Clone the QtWebEngine repository
- 2) Initialize the repository
- II. Build Instructions##
- 1) Generate the ninja build files by running qmake.
- 2) build with make
- 3) [optional] make install
- Additional tips and tricks
- Complete Upstream Chromium Checkout
- Use external Chromium sources
- Debug vs. Release builds
QtWebEngine - Combining the power of Chromium and Qt
To be able to build QtWebEngine you need Qt 5.2 or newer.
I. Getting the Code
1) Clone the QtWebEngine repository
git clone git://gitorious.org/qt-labs/qtwebengine.git2) Initialize the repository
This will fetch a snapshot of chromium sources we rely on.
./init-repository.pyII. Build Instructions##
1) Generate the ninja build files by running qmake.
It's a also possible to use qmake -r to forcefully re-gyp (without relying on make to determine if it's necessary).
qmake2) build with make
Everything should be set up properly now.
make3) [optional] make install
This step is required for installing l10n files and other resources (such as the resources for the remote inspector).
make installAdditional tips and tricks
Complete Upstream Chromium Checkout
If you want to have a complete chromium checkout with the complete history instead of the snapshot, then you can run the init-repository script with the -u option.
This will then create a complete ninja and chromium checkout in the subdirectory src/3rdparty_upstream. qmake will automatically pickup the location and make use of the sources in the subsequent steps II.1) and II.2).
./init-repository.py -uUse external Chromium sources
If you want to use external chromium sources instead of the submodule provided in the QtWebEngine repository, you can export the CHROMIUM_SRC_DIR variable point it to your source directory.
Debug vs. Release builds
By default, the configuration used for building Qt is followed. It is possible to override this by passing CONFIG+=release or debug at qmake time. e.g:
qmake -r CONFIG+=debug