1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
|
/****************************************************************************
**
** Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of the documentation of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:FDL$
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia. For licensing terms and
** conditions see http://qt.digia.com/licensing. For further information
** use the contact form at http://qt.digia.com/contact-us.
**
** GNU Free Documentation License Usage
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of
** this file. Please review the following information to ensure
** the GNU Free Documentation License version 1.3 requirements
** will be met: http://www.gnu.org/copyleft/fdl.html.
** $QT_END_LICENSE$
**
****************************************************************************/
/*!
\group platform-specific
\title Platform-Specific Documentation
\brief Documents describing platform-specific features of Qt.
These documents describe platform-specific features provided by Qt, and
discuss issues related to particular platforms and environments.
\generatelist{related}
*/
/*!
\page platform-notes.html
\ingroup platform-specific
\title Platform and Compiler Notes
\brief Information about the platforms on which Qt can be used.
This page contains information about the platforms Qt is currently known
to run on, with links to platform-specific notes, including any known bugs
or incompatibilities.
Information about the combinations of platforms and compilers
supported by Qt can be found on the \l{Supported Platforms} page.
\list
\li \l{Platform and Compiler Notes - X11}
\tableofcontents{1 Platform and Compiler Notes - X11}
\li \l{Platform and Compiler Notes - Windows}
\tableofcontents{1 Platform and Compiler Notes - Windows}
\li \l{Platform and Compiler Notes - Mac OS X}
\tableofcontents{1 Platform and Compiler Notes - Mac OS X}
\li \l{Platform and Compiler Notes - QNX}
\tableofcontents{1 Platform and Compiler Notes - QNX}
\li \l{Platform and Compiler Notes - VxWorks}
\tableofcontents{1 Platform and Compiler Notes - VxWorks}
\endlist
\section1 General Compiler Notes
\section2 Supported Features
Qt can be compiled with any compiler that is compliant with the C++98 standard. C++11
support is automatically enabled on compilers supporting it.
Building Qt is currently being tested on the following list of compilers:
\list
\li gcc 4.2.1 (Mac OS X only)
\li Apple clang 3.1 (Mac OS X / XCode 4)
\li gcc 4.5 and newer (Linux)
\li MSVC 2008 and newer
\li MingW 4.6
\li Intel CC (latest version)
\endlist
*/
/*!
\page platform-notes-x11.html
\title Platform and Compiler Notes - X11
\contentspage Platform and Compiler Notes
This page contains information about the X11 platforms Qt is currently
known to run on, with links to platform-specific notes. More information
about the combinations of platforms and compilers supported by Qt can be
found on the \l{Supported Platforms} page.
\tableofcontents
\section1 Linux
There are no known problems with using Qt on production versions of
Linux/x86, Linux/ppc, Linux/amd64 and Linux/ia64 (including Altix(R)).
For the GCC compiler, please also see the relevant
\l{Platform and Compiler Notes#General Compiler Notes}{General Compiler Notes}.
\section2 Installation problems
If you experience problems when installing new open source versions of Qt
versions, try to use the open source Qt archives (e.g., RPM)
provided by your Linux distribution. If you need to install the source (.tgz)
archive, be aware that you will probably end up with two different
versions of the Qt library installed on your system, which will probably
lead to link errors, like this:
\snippet doc/src/snippets/code/doc_src_platform-notes.qdoc 0
Fix this by removing the old version of the library.
If you have problems installing open source versions of Qt
provided by your Linux distribution (e.g., RPM), please consult the
maintainers of the distribution, not us.
Some RPM versions have problems installing some of the Qt RPM archives
where installation stops with an error message warning about a
"Failed Dependency". Use the \c{--nodeps} option to \c rpm to workaround
this problem.
\section2 Intel C++ Compiler for Linux
Qt can be compiled with the Intel C++ compile for Linux. The configuration is
not tested on a regular basis.
\section2 Known Issues with Intel C++ Compiler for Linux
\list
\li Precompiled header support does not work in version 10.0.025
and older. For these compilers, you should configure Qt with
-no-pch. Precompiled header support works properly in version
10.0.026 and later.
\li Version 10.0.026 for Intel 64 is known to miscompile qmake when
building in release mode. For now, configure Qt with
-debug. Version 10.1.008 and later can compile qmake in release
mode.
\li Versions 10.1.008 to 10.1.015 for both IA-32 and Intel 64 are
known crash with "(0): internal error: 0_47021" when compiling
QtXmlPatterns, QtWebKit, and Designer in release mode. Version
10.1.017 compiles these modules correctly in release mode.
\endlist
*/
/*!
\page platform-notes-windows.html
\title Platform and Compiler Notes - Windows
\contentspage Platform and Compiler Notes
This page contains information about the Windows platforms Qt is currently
known to run on, with links to platform-specific notes. More information
about the combinations of platforms and compilers supported by Qt can be
found on the \l{Supported Platforms} page.
\tableofcontents
\section1 Windows Vista, Windows 7, Windows 8
At the time Qt %VERSION% was released, there were no known issues on these
platforms.
\section1 Windows XP
\section2 Installation location
Installing Qt into a directory with spaces, e.g. C:\\Program Files, may
cause linker errors like the following:
\snippet doc/src/snippets/code/doc_src_platform-notes.qdoc 2
Install Qt into a subdirectory without spaces to avoid this problem.
\section2 Possible GL conflict
There is a known issue with running Microsoft NetMeeting, Lotus SameTime
and other applications that require screen grabbing while direct
rendering is enabled. Other GL-applications may not work as expected,
unless direct rendering is disabled.
\section2 GCC (MinGW)
We have tested Qt with this compiler on Windows XP.
The minimal version of MinGW
supported is GCC 4.6. For 64 bit builds, \l{TDM-GCC} can be used.
\section2 Intel C++ Compiler (Windows, Altix)
Qt has been tested successfully with:
\list
\li Windows - Intel(R) C++ Compiler for 32-bit applications,
Version 9.1.040.
\li Altix - Intel(R) C++ Itanium(R) Compiler for Itanium(R)-based
applications Version 8.1 Build 20050406 Package ID: l_cc_pc_8.1.030
\endlist
\section2 Visual Studio (Windows)
We do most of our Windows development on Windows 7, using Microsoft
Visual Studio 2008, Visual Studio 2010 or Visual Studio 11 (mostly
64bit).
We recommend using Visual Studio 2010 or higher as it supports some
C++11 features beneficial to performance and memory usage.
Qt works with all editions of Visual Studio.
In order to use Qt with the Visual Studio Express Editions
you need to download and install the Windows SDK.
The Visual C++ Linker doesn't understand filenames with spaces (as in
\c{C:\Program files\Qt\}) so you will have to move it to another place,
or explicitly set the path yourself; for example:
\snippet doc/src/snippets/code/doc_src_compiler-notes.qdoc 0
If you are experiencing strange problems with using special flags that
modify the alignment of structure and union members (such as \c{/Zp2})
then you will need to recompile Qt with the flags set for the
application as well.
Visual Studio 2010 should be updated to Service Pack 1. Otherwise, a
problem when compiling Qt for 64-bit in release mode may occur (see
http://support.microsoft.com/kb/2280741).
*/
/*!
\page platform-notes-mac.html
\title Platform and Compiler Notes - Mac OS X
\contentspage Platform and Compiler Notes
This page contains information about the Mac OS X versions Qt is currently
known to run on, with links to platform-specific notes. More information
about the combinations of platforms and compilers supported by Qt can be
found on the \l{Supported Platforms} page.
\tableofcontents
\section1 General Information
Qt 5 applications can be deployed on Mac OS X 10.6 (Snow Leopard)
and higher. We recommend using the most recent version of Mac OS
for developing applications. Qt binaries built on 10.7 can be
deployed on 10.6.
\section2 Required Compiler Versions
Use the latest gcc or clang as supplied with Xcode. Currently
tested versions are Apple gcc 4.2.1 and Apple clang version 3.1.
\section2 Binary Package
\section2 Mac OS X on PowerPC hardware
Qt 5 does not support OS X on PowerPC.
\section2 Fink
If you have installed the Qt for X11 package from \l{Fink},
it will set the QMAKESPEC environment variable to darwin-g++. This will
cause problems when you build the Qt for Mac OS X package. To fix this, simply
unset your QMAKESPEC or set it to macx-g++ before you run configure.
You need to have a fresh Qt distribution (make confclean).
\section2 MySQL and Mac OS X
There seems to be a issue when both -prebind and -multi_module are
defined when linking static C libraries into dynamic library. If you
get the following error message when linking Qt:
\snippet doc/src/snippets/code/doc_src_platform-notes.qdoc 6
re-link Qt using -single_module. This is only a problem when building the
MySQL driver into Qt. It does not affect plugins or static builds.
\section2 Attributes
The following lists a set of useful attributes that can be used to tweak applications
on Mac:
Qt::AA_MacPluginApplication, Qt::AA_DontUseNativeMenuBar, Qt::AA_MacDontSwapCtrlAndMeta
Qt::WA_MacNoClickThrough, Qt::WA_MacOpaqueSizeGrip, Qt::WA_MacShowFocusRect,
Qt::WA_MacNormalSize, Qt::WA_MacSmallSize, Qt::WA_MacMiniSize, Qt::WA_MacVariableSize,
Qt::WA_MacBrushedMetal, Qt::WA_MacAlwaysShowToolWindow, Qt::WA_MacFrameworkScaled,
Qt::WA_MacNoShadow, Qt::Sheet, Qt::Drawer, Qt::MacWindowToolBarButtonHint,
QMainWindow::unifiedTitleAndToolBarOnMac
\section2 Mixing Qt with native code
Two classes are available for either adding native Cocoa views/controls
inside a Qt application, or the opposite, embedding Qt into a native
Cocoa application:
QMacCocoaViewContainer, QMacNativeWidget
\section3 Using native Cocoa panels
Launching native Cocoa panels from within a Qt application can sometimes
be problematic. The reason is that Qt's event dispatcher is more flexible
than what Cocoa offers, and lets the user spin the event dispatcher (and
running QEventLoop::exec) without having to think about whether or not modal
dialogs are showing on screen (which is a difference to Cocoa). Therefore
we need to do special bookkeeping in Qt to handle this correctly, which
unfortunately make mixing in native panels hard. The best way at the moment
to do this, is to follow the pattern below, where we post the call to the
function with native code rather than calling it directly. Then we know that
Qt has cleanly updated any pending event loop recursions before the native
panel is shown:
\code
#include <QtGui>
class NativeProxyObject : public QObject
{
Q_OBJECT
public slots:
void execNativeDialogLater()
{
QMetaObject::invokeMethod(this, "execNativeDialogNow", Qt::QueuedConnection);
}
void execNativeDialogNow()
{
NSRunAlertPanel(@"A Native dialog", @"", @"OK", @"", @"");
}
};
#include "main.moc"
int main(int argc, char **argv){
QApplication app(argc, argv);
NativeProxyObject proxy;
QPushButton button("Show native dialog");
QObject::connect(&button, SIGNAL(clicked()), &proxy, SLOT(execNativeDialogLater()));
button.show();
return app.exec();
}
\endcode
*/
|