Changes between Version 2 and Version 3 of QtWebKitPackaging

Timestamp:

May 4, 2010, 7:52:05 AM (15 years ago)

Author:

Simon Hausmann

Comment:

--

QtWebKitPackaging

@@ -5 +5 @@
 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.
 
-== Source Package Requirements ==
-
-   * A source package should be self-contained and not depend on other source package.
-   * It should be possible to compile the package against an installed version of Qt.
-   * No additional tools should be required for the build, beyond what is needed for building Qt applications.
-   * After the build and installation of the source package it should be possible to use the new QtWebKit installation through simple "QT += webkit" use in the .pro file.
-
 == Packaging Steps ==
 
-The {{{make-package}}} 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.
+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.
 
-   1. qmake is run to generate all the automatically generated code.
-   1. syncqt from Qt is run to generate the convenience class-name style includes, located in {{{include/QtWebKit}}}
+   1. qmake is run to generate all the automatically generated code in the {{{generated/}}} subdirectories.
+   1. Unnecessary files and directories are removed.
+   1. A source tar.gz is produced.
 
+Calling the tool produces a package from the current git {{{HEAD}}}.
+