QtWebKit Packaging
The goal of the packaging is to take a version of WebKit and produce a tar/zip file that contains the source in a way that makes it easy for third-party developers to compile and install. After installation it should be easy to use the produced library in the application. Up to Qt-4.8, this is the way QtWebKit is integrated into the Qt repository.
In addition we should think about building binary packages from that source package, including perhaps the option of providing binaries that can be installed on devices.
Packaging Steps
The make-package.py tool from http://gitorious.org/qtwebkit/tools is currently used to create source packages. It assumes the availability of the source code in a Git repository.
- qmake is run to generate all the automatically generated code in the
generated/subdirectories. (make sure your current qmake points to the Qt repository you want to integrate) - Unnecessary files and directories are removed.
- The sha1 of the last included commit is stored in
.tag, to make it possible to find out from which commit a source package was created from. - A source tar.gz is produced.
Calling the tool produces a package from the current git HEAD.
Integrating Steps
The integrate-package-into-qt tool from http://gitorious.org/qtwebkit/tools is currently used to import the tarball created to the source tree of Qt.
- Run the script with the tarball path in parameter within the source qt repository.
- Verify that no extra files are added by mistake (e.g. DerivedSources.pro).
- Commit and push after checking the changes.
Alternatively you can cherry pick particular changes by using webkit-pick-into-qt.
