0
|
1 |
INSTALLING Qt Source Package Version %VERSION%.
|
|
2 |
|
|
3 |
1. If you have the commercial edition of Qt, install your license
|
|
4 |
file as $HOME/.qt-license if you are on Unix. If you are on
|
|
5 |
Windows, copy the license file into your home directory
|
|
6 |
(this may be known as the userprofile environment variable) and
|
|
7 |
rename it to .qt-license. For example on Windows XP,
|
|
8 |
%USERPROFILE% should be something like C:\Documents and
|
|
9 |
Settings\username.
|
|
10 |
|
|
11 |
For the open source version you do not need a license file.
|
|
12 |
|
|
13 |
2. Unpack the archive if you have not done so already:
|
|
14 |
|
|
15 |
On Unix (X11 and Mac):
|
|
16 |
cd /tmp
|
|
17 |
gunzip %DISTNAME%.tar.gz # uncompress the archive
|
|
18 |
tar xvf %DISTNAME%.tar # unpack it
|
|
19 |
|
|
20 |
This creates the directory /tmp/%DISTNAME% containing the files
|
|
21 |
from the archive. We only support the GNU version of the tar
|
|
22 |
archiving utility. Note that on some systems it is called gtar.
|
|
23 |
|
|
24 |
On Windows, uncompress the files into the directory you want Qt
|
|
25 |
installed, e.g. C:\Qt\%VERSION%.
|
|
26 |
|
|
27 |
NOTE: The install path must not contain any spaces.
|
|
28 |
|
|
29 |
4. Environment variables
|
|
30 |
|
|
31 |
In order to build and use Qt, the PATH environment variable needs
|
|
32 |
to be extended to locate qmake, moc and other Qt tools
|
|
33 |
|
|
34 |
On Windows, this is done by adding C:\Qt\%VERSION%\bin
|
|
35 |
to the PATH variable. On Unix, this is done by adding
|
|
36 |
/tmp/%DISTNAME%.
|
|
37 |
|
|
38 |
For newer versions of Windows, PATH can be extended through
|
|
39 |
"Control Panel->System->Advanced->Environment variables" and for
|
|
40 |
older versions by editing C:\autoexec.bat.
|
|
41 |
|
|
42 |
In .profile (if your Unix shell is bash), add the following lines:
|
|
43 |
|
|
44 |
PATH=/usr/local/Trolltech/Qt-%VERSION%/bin:$PATH
|
|
45 |
export PATH
|
|
46 |
|
|
47 |
In .login (in case your Unix shell is csh or tcsh), add the following line:
|
|
48 |
|
|
49 |
setenv PATH /usr/local/Trolltech/Qt-%VERSION%/bin:$PATH
|
|
50 |
|
|
51 |
If you use a different Unix shell, please modify your environment
|
|
52 |
variables accordingly.
|
|
53 |
|
|
54 |
For some X11 compilers that do not support rpath you must also
|
|
55 |
extended the LD_LIBRARY_PATH environment variable to include
|
|
56 |
/usr/local/Trolltech/Qt-%VERSION%/lib. On Linux or Mac with GCC
|
|
57 |
this step is not needed.
|
|
58 |
|
|
59 |
4. Building
|
|
60 |
|
|
61 |
4.1 Building on Unix
|
|
62 |
|
|
63 |
To configure the Qt library for your machine type, run the
|
|
64 |
./configure script in the package directory.
|
|
65 |
|
|
66 |
By default, Qt is configured for installation in the
|
|
67 |
/usr/local/Trolltech/Qt-%VERSION% directory, but this can be
|
|
68 |
changed by using the -prefix option.
|
|
69 |
|
|
70 |
cd /tmp/%DISTNAME%
|
|
71 |
./configure
|
|
72 |
|
|
73 |
Type "./configure -help" to get a list of all available options.
|
|
74 |
|
|
75 |
To create the library and compile all the demos, examples, tools,
|
|
76 |
and tutorials, type:
|
|
77 |
|
|
78 |
make
|
|
79 |
|
|
80 |
If you did not configure Qt using the -prefix-install option,
|
|
81 |
you need to install the library, demos, examples, tools, and
|
|
82 |
tutorials in the appropriate place. To do this, type:
|
|
83 |
|
|
84 |
su -c "make install"
|
|
85 |
|
|
86 |
and enter the root password. On some systems, you have to use the
|
|
87 |
sudo command as follows:
|
|
88 |
|
|
89 |
sudo make install
|
|
90 |
|
|
91 |
and enter your password, this requires that you have administrator access
|
|
92 |
to your machine.
|
|
93 |
|
|
94 |
Note that on some systems the make utility is named differently,
|
|
95 |
e.g. gmake. The configure script tells you which make utility to
|
|
96 |
use.
|
|
97 |
|
|
98 |
If you need to reconfigure and rebuild Qt from the same location,
|
|
99 |
ensure that all traces of the previous configuration are removed
|
|
100 |
by entering the build directory and typing
|
|
101 |
|
|
102 |
make confclean
|
|
103 |
|
|
104 |
before running the configure script again.
|
|
105 |
|
|
106 |
4.2 Building on Windows
|
|
107 |
|
|
108 |
To configure the Qt library for your machine type:
|
|
109 |
|
|
110 |
C:
|
|
111 |
cd \Qt\%VERSION%
|
|
112 |
configure
|
|
113 |
|
|
114 |
Type "configure -help" to get a list of all available options.
|
|
115 |
|
|
116 |
If you are using the "-direct3d" option, make sure that you have
|
|
117 |
the Direct3D SDK installed, and that you have run the
|
|
118 |
%DXSDK_DIR%\Utilities\Bin\dx_setenv.cmd command, before attempting
|
|
119 |
to run configure.
|
|
120 |
|
|
121 |
The actual commands needed to build Qt depends on your development
|
|
122 |
system. For Microsoft Visual Studio to create the library and
|
|
123 |
compile all the demos, examples, tools and tutorials type:
|
|
124 |
|
|
125 |
nmake
|
|
126 |
|
|
127 |
If you need to reconfigure and rebuild Qt from the same location,
|
|
128 |
ensure that all traces of the previous configuration are removed
|
|
129 |
by entering the build directory and typing
|
|
130 |
|
|
131 |
nmake confclean
|
|
132 |
|
|
133 |
before running the configure script again.
|
|
134 |
|
|
135 |
5. That's all. Qt is now installed.
|
|
136 |
|
|
137 |
If you are new to Qt, we suggest that you take a look at the demos
|
|
138 |
and examples to see Qt in action. Run the Qt Examples and Demos
|
|
139 |
either by typing 'qtdemo' on the command line or through the
|
|
140 |
desktop's Start menu.
|
|
141 |
|
|
142 |
You might also want to try the following links:
|
|
143 |
|
|
144 |
http://qt.nokia.com/doc/%VERSION%/how-to-learn-qt.html
|
|
145 |
http://qt.nokia.com/doc/%VERSION%/tutorial.html
|
|
146 |
http://qt.nokia.com/developer
|
|
147 |
|
|
148 |
We hope you will enjoy using Qt. Good luck!
|