source: trunk/README.OS2@ 243

Last change on this file since 243 was 243, checked in by Dmitry A. Kuminov, 16 years ago

Readme for Beta 3.

File size: 10.1 KB
Line 
1This is Beta 2 of Qt version 4.5.1 for OS/2 and eCS.
2
3This document contains a brief information on the OS/2 version of the Qt library
4plus a brief list of OS/2-specific changes from release to release (section
5CHANGES below). Please visit the project page at
6
7 http://svn.netlabs.org/qt4/wiki
8
9to get more information and the latest news and also to report bugs.
10
11
12
13REQUIREMENTS
14
15In order to compile the Qt library, you will need the following tools:
16
17 - One of the OS/2 Warp 4, OS/2 Warp 4.5 or eComStation operating systems.
18
19 - InnoTek GCC compiler version 3.3.5 CSD3 or above (not tested).
20 You can download a copy of the compiler using the following link:
21
22 ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd3.zip
23
24 - Patched OpenWatcom linker which you can download from:
25
26 ftp://ftp.netlabs.org/pub/gcc/wl-hll-r1.zip
27
28 Note that if you use IBM ILINK (no matter what version), you will
29 not be able to build the debug version of the library due to
30 bugs/limitations of ILINK.
31
32 - GNU Make 3.81beta1 or above (not tested) available at:
33
34 http://unix.os2site.com/pub/binary/make/make-3_81beta1-bin-static.zip
35
36After unpacking the GCC archive, you will have to set up the compiler
37environment by invoking gccenv.cmd from the bin subdirectory with the
38correct arguments (type gccenv.cmd -? for help). For the OpenWatcom
39linker, specify WLINK as the second argument. You will also need to perform
40the following steps:
41
42 - Make sure the selected linker and the make utility are in PATH.
43
44 - Make sure CMD.EXE is your command line processor (the generated makefiles
45 will rely on its 'copy', 'if' and other commands).
46
47 - set LIBRARY_PATH=C:\OS2\DLL;C:\MPTN\DLL where C: is your boot drive.
48
49Note that the QTDIR environment variable used by previous Qt versions is not
50used by Qt4 anymore (except two rare cases that do not affect the OS/2 platform
51anyway and are probably leftovers after the migration of the qmake feature
52specifications to Qt4). Therefore, there is no need to set this variable
53explicitly. See a note below about
54
55There is also no need to set the QMAKESPEC variable explicitly. If it is absent,
56qmake will use the specification stored in the <Qt4_Home>/mkspecs/default
57directory, which on OS/2 always refers to the "os2-g++" specification, the only
58one supported at the present time.
59
60When the environment is set up, go to the directory where you unpacked the
61Qt4 source tree and type:
62
63 configure.cmd
64
65This will set up the library (create necessary configuration and include files)
66and build the qmake utility.
67
68The next step is to go to the src subdirectory and type:
69
70 make
71
72This will compile and link the library. Note that by default both the release
73and the debug version of the library are built (please be patient, it may take
74quite some time depending on your hardware). The release and debug libraries can
75co-exist in the same source tree and may be used in parallel: all the debug DLLs
76get a 'd' letter in their name preceeding the Qt major version number and use
77separate directories for object files.
78
79To save time, you may also build the release and the debug versions of the
80library separately by typing 'make release' or 'make debug' accordingly
81instead of just 'make'.
82
83Once the library is successfully built, you may try to compile the demos
84and examples by visiting the individual example subdirectories in the source
85tree and typing 'qmake' followed by one of 'make', 'make release' or