Changeset 983 for trunk/README.OS2

Timestamp:

Aug 15, 2011, 2:57:00 PM (14 years ago)

Author:

Dmitry A. Kuminov

Message:

OS/2: Add support for shadow builds of Qt itself.

File:

• trunk/README.OS2 (modified) (2 diffs)

trunk/README.OS2

@@ -56 +56 @@
 script (discussed in section "COMPILING QT" below) will automatically disable
 the corresponding feature:
+
+  - Perl 5.8.2 or above. This is required if you want to perform a shadow build
+    of the Qt library (which is a recommended way to go). Please refer to
+    section "COMPILING QT" for more information about shadow builds. Recent
+    builds of Perl for OS/2 are available here:
+
+      http://os2ports.smedley.info/index.php?page=perl
 
   - MAPSYM 4.00.000 (Oct 4 2001) to enable generation of symbol (.SYM) files for
@@ -232 +239 @@
 libraries) and proceed directly to the next section.
 
-When the environment is set up, go to the directory where you unpacked the
-Qt4 source tree and type:
-
-  configure.cmd
-
-This will set up the Qt library (by creating necessary configuration and include
-files and a bunch of Makefiles for variuos components) and build the qmake tool.
-
-The next step is to type:
-
-  make
-
-This will compile and link the Qt library. Note that by default both the release
-and the debug version of the library are built (please be patient, it may take
-quite some time depending on your hardware). The release and debug libraries can
-co-exist in the same source tree and may be used in parallel: all the debug DLLs
-get a 'd' letter in their name preceeding the Qt major version number and use
-separate directories for object files.
-
-To save time, you may build the release and the debug versions of the Qt library
-separately by typing 'make release' or 'make debug' accordingly instead of just
-'make'.
+When the environment is set up as described above, you may build the Qt library.
+There are two distinct ways of doing this: in the source tree or in a separate
+directory of your choice. In the first case, all results of the build process
+(intermediate object files as well as final executables and DLLs) will be placed
+right in the source tree. In the second case, they will be placed in the
+separate directory -- this is called a shadow build.
+
+Shadow builds are the recommended way to go because they keep the source
+directories clean and also allow to use the same source tree for creating any
+number of builds, each with its own build options.
+
+To perform a shadow build, do the following steps:
+
+  1. Create a directory outside the Qt4 source tree.
+
+  2. Go to that directory.
+
+  3. Type:
+
+     <source_tree>\configure.cmd
+
+     where <source_tree> is the directory containing the Qt4 source tree. This
+     will create all necessary configuration files, headers, Makefiles and will
+     also build the qmake tool which is necessary to control the rest of the
+     build process (note that building qmake will take some time).
+
+  4. Once the configure process is finished, type:
+
+     make
+
+  Note that by the default the shadow build will produce the release version of
+  the Qt library. This may be changed by passing command line options to
+  configure.cmd at step 3.
+
+To perform a normal build, you execute 'configure.cmd' followed by 'make' right
+in the directory containing the Qt4 source tree. The default in this case is to
+build both the debug and release versions of the Qt library.
+
+Please keep in mind that in case of the dual debug and release build (where both
+flavors are stored in the same build directory), only DLL and LIB files will be
+separated (because the debug versions of them will have the 'd' suffix in the
+file name). Executable files are normally taken from the release build but,
+since the file names are identical, sometimes they may be overwritten by the
+debug versions (e.g. when you rebuild parts of the library later). For this
+reason, performing dual builds is not recommended.
+
+The Qt library is huge so the build process will take several hours (or even
+several dozen of hours) depending on your hardware and configure options.
 
 Once the library is successfully built, you may try to compile the demos and
 examples by visiting the individual example subdirectories in the source tree
-and typing 'qmake' followed by one of 'make', 'make release' or 'make debug'
-in that subdirectory.
+and typing 'qmake' followed by 'make'.
 
 NOTE: