source: trunk/README.OS2@ 204

This is Beta 2 of Qt version 4.5.1 for OS/2 and eCS.

This document contains a brief information on the OS/2 version of the Qt library
plus a brief list of OS/2-specific changes from release to release (section
CHANGES below). Please visit the project page at

  http://svn.netlabs.org/qt4/wiki

to get more information and the latest news and also to report bugs.



REQUIREMENTS

In order to compile the Qt library, you will need the following tools:

  - One of the OS/2 Warp 4, OS/2 Warp 4.5 or eComStation operating systems.

  - InnoTek GCC compiler version 3.3.5 CSD3 or above (not tested).
    You can download a copy of the compiler using the following link:

      ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd3.zip

  - Patched OpenWatcom linker which you can download from:

      ftp://ftp.netlabs.org/pub/gcc/wl-hll-r1.zip

    Note that if you use IBM ILINK (no matter what version), you will
    not be able to build the debug version of the library due to
    bugs/limitations of ILINK.

  - GNU Make 3.81beta1 or above (not tested) available at:

      http://unix.os2site.com/pub/binary/make/make-3_81beta1-bin-static.zip

After unpacking the GCC archive, you will have to set up the compiler
environment by invoking gccenv.cmd from the bin subdirectory with the
correct arguments (type gccenv.cmd -? for help). For the OpenWatcom
linker, specify WLINK as the second argument. You will also need to perform
the following steps:

  - Make sure the selected linker and the make utility are in PATH.

  - Make sure CMD.EXE is your command line processor (the generated makefiles
    will rely on its 'copy', 'if' and other commands).

  - set LIBRARY_PATH=C:\OS2\DLL;C:\MPTN\DLL where C: is your boot drive.

Note that the QTDIR environment variable used by previous Qt versions is not
used by Qt4 anymore (except two rare cases that do not affect the OS/2 platform
anyway and are probably leftovers after the migration of the qmake feature
specifications to Qt4). Therefore, there is no need to set this variable
explicitly. See a note below about

There is also no need to set the QMAKESPEC variable explicitly. If it is absent,
qmake will use the specification stored in the <Qt4_Home>/mkspecs/default
directory, which on OS/2 always refers to the "os2-g++" specification, the only
one supported at the present time.

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 library (create necessary configuration and include files)
and build the qmake utility.

The next step is to go to the src subdirectory and type:

  qmake
  make

This will compile and link the 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.

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.

NOTE:

  Please keep in mind that due to dropping the QTDIR variable recognition,
  qmake.exe now unconditionally uses hard-coded paths to locate various Qt4
  components (such as the include or source directory) during the makefile
  generation process and therefore if you move the Qt source tree to another
  location you will need to run configure.cmd again in order to update these
  hard-coded paths and rebuild qmake and other dependent parts of the library.