| 1 | <?xml version="1.0" encoding="UTF-8"?> | 
|---|
| 2 | <?xml-stylesheet type="text/css" | 
|---|
| 3 | href="file:qtos2-xxe.css" | 
|---|
| 4 | ?> | 
|---|
| 5 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" | 
|---|
| 6 | "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> | 
|---|
| 7 | <html> | 
|---|
| 8 | <head> | 
|---|
| 9 | <link href="qtos2-www.css" rel="stylesheet" type="text/css" /> | 
|---|
| 10 |  | 
|---|
| 11 | <title>Qt Toolkit Version 3 for OS/2</title> | 
|---|
| 12 | </head> | 
|---|
| 13 |  | 
|---|
| 14 | <body id="install"> | 
|---|
| 15 | <h1><a name="top">Installation</a></h1> | 
|---|
| 16 |  | 
|---|
| 17 | <p>This section describes how to install, configure and build the Qt | 
|---|
| 18 | Toolkit under OS/2.</p> | 
|---|
| 19 |  | 
|---|
| 20 | <h2><a name="Requirements">Requirements</a></h2> | 
|---|
| 21 |  | 
|---|
| 22 | <p>In order to build the Qt Toolkit Version 3 under OS/2 or eComStation | 
|---|
| 23 | you need the following tools:</p> | 
|---|
| 24 |  | 
|---|
| 25 | <ul> | 
|---|
| 26 | <li>Compiler: <a | 
|---|
| 27 | href="http://www.innotek.de/products/gccos2/download/gccos2download_e.html">Innotek | 
|---|
| 28 | GCC 3.3.2 for OS/2 beta 4</a> updated to <a | 
|---|
| 29 | href="http://www.innotek.de/products/gccos2/download/gccos2download_e.html">CSD1</a>.<br />Download | 
|---|
| 30 | and install according to the installation instructions | 
|---|
| 31 | (<kbd>usr\doc\GCC-3.2.2\Install.os2</kbd>).</li> | 
|---|
| 32 |  | 
|---|
| 33 | <li>Linker: IBM ILINK 3.08, a part of the IBM Visual Age C/C++ 3 | 
|---|
| 34 | distribution updated to version 3.08.<br />You need only two files, | 
|---|
| 35 | <kbd>BIN\ILINK.EXE</kbd> and <kbd>DLL\CPPOM30.DLL</kbd>. If you already | 
|---|
| 36 | have IBM Visual Age C/C++ installed, you don't need to do anything else. | 
|---|
| 37 | Otherwise, copy the above two files to some directory.<br /><b>Note:</b> | 
|---|
| 38 | A separate distribution of IBM ILINK 5.0 available through the software | 
|---|
| 39 | subscription will not work, because it has some serious bugs related to | 
|---|
| 40 | exporting large amounts of symbols.</li> | 
|---|
| 41 |  | 
|---|
| 42 | <li>Make utility: <a | 
|---|
| 43 | href="http://www.unixos2.org/sw/pub/binary/make/make-3_81beta1-bin-static.zip">GNU | 
|---|
| 44 | Make 3.81beta1</a>. Just unzip the file <kbd>make.exe</kbd> to some | 
|---|
| 45 | directory.</li> | 
|---|
| 46 | </ul> | 
|---|
| 47 |  | 
|---|
| 48 | <p>Check that the above tooks work, and then proceed to the following | 
|---|
| 49 | step.</p> | 
|---|
| 50 |  | 
|---|
| 51 | <h2><a name="BuildingQt">Building Qt</a></h2> | 
|---|
| 52 |  | 
|---|
| 53 | <ol> | 
|---|
| 54 | <li>Unzip the contents of the Qt for OS/2 distribution archive to some | 
|---|
| 55 | directory.</li> | 
|---|
| 56 |  | 
|---|
| 57 | <li>Go to that directory, run the <kbd>configure.cmd</kbd> script and | 
|---|
| 58 | follow on-screen instructions.<br />You will be prompted to enter | 
|---|
| 59 | directories where the script will search for the required tools and to | 
|---|
| 60 | configure the library type you want to build. Note that it is not | 
|---|
| 61 | necessary to remember a full path to a tool -- you can specify an | 
|---|
| 62 | upper-level directory or simply a root directory of the drive you have | 
|---|
| 63 | installed the tools onto.</li> | 
|---|
| 64 |  | 
|---|
| 65 | <li>Wait until the compilation process is finished.</li> | 
|---|
| 66 | </ol> | 
|---|
| 67 |  | 
|---|
| 68 | <p>If the compilation process fails, you can inspect the file | 
|---|
| 69 | <kbd>build.log</kbd> created in the installation directory.</p> | 
|---|
| 70 |  | 
|---|
| 71 | <p>After the Qt library is successfully compiled and built, it is | 
|---|
| 72 | recommended that you place the <kbd>qt.cmd</kbd> script that was generated | 
|---|
| 73 | in the installation directory to some of the directories listed in your | 
|---|
| 74 | <kbd>PATH</kbd> environment variable and use it as a command line wrapper | 
|---|
| 75 | to work with the Qt Toolkit: run tutorials and examples, compile your own | 
|---|
| 76 | programs, etc. The script sets up the environment necessary for the Qt | 
|---|
| 77 | Toolkit and for all other tools and simply passes all command line | 
|---|
| 78 | arguments to the command line interpreter. For example, in order to run | 
|---|
| 79 | the last Qt tutorial application, go to the subdirectory | 
|---|
| 80 | <kbd>tutorial\t14</kbd> located inside the installation directory and | 
|---|
| 81 | execute the following command (provided that you have already placed | 
|---|
| 82 | <kbd>qt.cmd</kbd> somewhere in the <kbd>PATH</kbd>):</p> | 
|---|
| 83 |  | 
|---|
| 84 | <pre>qt.cmd t14.exe</pre> | 
|---|
| 85 |  | 
|---|
| 86 | <p>To recompile the tutorial you can type</p> | 
|---|
| 87 |  | 
|---|
| 88 | <pre>qt.cmd make</pre> | 
|---|
| 89 | </body> | 
|---|
| 90 | </html> | 
|---|