| [544] | 1 | HOW TO PREPARE AN OFFICIAL BUILD OF QT4 FOR OS/2
|
|---|
| 2 |
|
|---|
| 3 | 1. Define the SVN revision for the build (referred to as REV below),
|
|---|
| 4 | and the path where the source tree will be exported (referred to as
|
|---|
| 5 | TREE). The usual format for TREE is:
|
|---|
| 6 |
|
|---|
| 7 | qt-all-opensource-src-X.Y.Z-os2-BUILD
|
|---|
| 8 |
|
|---|
| 9 | Where X.Y.Z are major, minor and patch Qt version numbers (e.g. 4.5.1)
|
|---|
| 10 | and BUILD is a human readable build name (e.g. beta5). Note that BUILD
|
|---|
| 11 | will be empty if this is an original GA build of the given version. The
|
|---|
| 12 | preceeding dash in the examples below will also disappear in this case.
|
|---|
| 13 |
|
|---|
| 14 | 2. Do `svn export -r REV http://svn.netlabs.org/repos/qt4/trunk TREE'.
|
|---|
| 15 |
|
|---|
| 16 | 3. Do `zip -SrX9 qt-all-opensource-src-X_Y_Z-os2-BUILD.zip TREE/'.
|
|---|
| 17 | This will be the source distribution.
|
|---|
| 18 |
|
|---|
| 19 | 4. Do `svn co http://svn.netlabs.org/repos/qt4/trunk PKG'.
|
|---|
| 20 |
|
|---|
| 21 | 5. Go to PKG and execute the following script:
|
|---|
| 22 |
|
|---|
| 23 | make_packages.cmd TREE REV BUILD OUT
|
|---|
| 24 |
|
|---|
| 25 | where TREE is the tree where the fresh revision REV is checked out, BUILD
|
|---|
| 26 | is the short human readable build name (such as "Beta 5" or "GA") and OUT
|
|---|
| 27 | is the output directory where all created packages and itermediate files
|
|---|
| 28 | will go.
|
|---|
| 29 |
|
|---|
| 30 | The above script is designed to be completely automatic. It will perform
|
|---|
| 31 | the following steps:
|
|---|
| 32 |
|
|---|
| 33 | 1) Run TREE\configure.cmd with all the necessary options.
|
|---|
| 34 |
|
|---|
| 35 | 2) Run `make install' in the TREE which will first create an official
|
|---|
| 36 | reelase build of everything (library, tools, examples, demos) and then
|
|---|
| 37 | fake-install it to a temporary directory in OUT.
|
|---|
| 38 |
|
|---|
| 39 | 3) Gather the installed files to separate packages and generate .WPI archives
|
|---|
| 40 | out of them. Currently, the following archives are generated in OUT:
|
|---|
| 41 |
|
|---|
| 42 | qt-lib-X_Y_Z-BUILD.wpi - Runtime DLLs and binaries
|
|---|
| 43 | qt-dev-X_Y_Z-BUILD.wpi - Development libraries and headers
|
|---|
| 44 | qt-examples-X_Y_Z-BUILD.wpi - Demo and example apps with sources
|
|---|
| 45 |
|
|---|
| 46 | The script puts all output to "PKG\make_packages.log" which you may examine
|
|---|
| 47 | if something goes wrong. While the script provides special options for
|
|---|
| 48 | continuing the failed build, they may only be used if you understand what
|
|---|
| 49 | is wrong and how to seamlessly fix it w/o invalidating the generated output.
|
|---|
| 50 |
|
|---|
| 51 | 6. Upload the created .ZIP and .WPI archives to ftp://ftp.netlabs.org/pub/qt4
|
|---|
| 52 | and make an announcement at http://svn.netlabs.org/qt4/wiki.
|
|---|
| 53 |
|
|---|
| 54 | 7. That should be it.
|
|---|
| 55 |
|
|---|
