HOW TO PREPARE AN OFFICIAL BUILD OF QT4 FOR OS/2

1. Define the SVN revision for the build (referred to as REV below),
   and the path where the source tree will be exported (referred to as
   TREE). The usual format for TREE is:

     qt-all-opensource-src-X.Y.Z-os2-BUILD

   Where X.Y.Z are major, minor and patch Qt version numbers (e.g. 4.5.1)
   and BUILD is a human readable build name (e.g. beta5). Note that BUILD
   will be empty if this is an original GA build of the given version. The
   preceeding dash in the examples below will also disappear in this case.

2. Do `svn export -r REV http://svn.netlabs.org/repos/qt4/trunk TREE'.

3. Do `zip -SrX9 qt-all-opensource-src-X_Y_Z-os2-BUILD.zip TREE/'.
   This will be the source distribution.

4. Do `svn co http://svn.netlabs.org/repos/qt4/trunk PKG'.

5. Go to PKG and execute the following script:

    make_packages.cmd TREE REV BUILD OUT

   where TREE is the tree where the fresh revision REV is checked out, BUILD
   is the short human readable build name (such as "Beta 5" or "GA") and OUT
   is the output directory where all created packages and itermediate files
   will go.

   The above script is designed to be completely automatic. It will perform
   the following steps:

   1) Run TREE\configure.cmd with all the necessary options.

   2) Run `make install' in the TREE which will first create an official
      reelase build of everything (library, tools, examples, demos) and then
      fake-install it to a temporary directory in OUT.

   3) Gather the installed files to separate packages and generate .WPI archives
      out of them. Currently, the following archives are generated in OUT:

      qt-lib-X_Y_Z-BUILD.wpi        - Runtime DLLs and binaries
      qt-dev-X_Y_Z-BUILD.wpi        - Development libraries and headers
      qt-examples-X_Y_Z-BUILD.wpi   - Demo and example apps with sources

   The script puts all output to "PKG\make_packages.log" which you may examine
   if something goes wrong. While the script provides special options for
   continuing the failed build, they may only be used if you understand what
   is wrong and how to seamlessly fix it w/o invalidating the generated output.

6. Upload the created .ZIP and .WPI archives to ftp://ftp.netlabs.org/pub/qt4
   and make an announcement at http://svn.netlabs.org/qt4/wiki.

7. That should be it.