Newer Older
Qt Creator 2.0.80
con's avatar
con committed
Kai Koehne's avatar
Kai Koehne committed
Qt Creator is a crossplatform C++ IDE for development with the Qt framework.
con's avatar
con committed
4 5 6

Supported Platforms
con's avatar
con committed
The binary packages support the following platforms:
con's avatar
con committed
8 9

Windows XP SP2, Windows Vista
con's avatar
con committed
(K)Ubuntu Linux 7.04 32bit and 64bit
con's avatar
con committed
11 12
Mac OS 10.4 and later

Building the sources requires Qt 4.7.0 or later.
con's avatar
con committed

con's avatar
con committed
15 16 17
Compiling Qt Creator
   * Qt 4.7
con's avatar
con committed
19 20 21
   * On Windows: mingw 4.4 or later, Visual Studio 2008 or later
   * On Mac: XCode 2.5 or later

Kai Koehne's avatar
Kai Koehne committed
22 23
We recommend that you build Qt Creator not in the source directory, but in a
separate directory. To do that, use the following commands:
con's avatar
con committed
24 25 26 27 28
make (or mingw32-make or nmake or jom, depending on your platform)

29 30 31 32 33 34
Qml Support

Define the QTCREATOR_WITH_QML environment variable to enable Qml support
(before running qmake).

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
QmlDesigner, QmlInspector require private headers

The QmlDesigner and QmlInspector plugins depend on "private" Qt headers,
specifically from the QtDeclarative module. These private headers always end
with an "_p.h", and Nokia does not make any promises to keep the files or API's
binary or source compatible between releases. This means that when compiled,
the two plugins have a dependency to the exact Qt version they were compiled
with. Running Qt Creator with the plugins against updated Qt libraries (also for
patch releases) might lead to link time failures, or even crashes.

If you want to disable the plugins, you can pass "QT_PRIVATE_HEADERS=" to qmake:


Anyhow, the plugins will not be compiled when the private header files needed
are not found. This might be the case when you are using a Qt version from your
distribution, or when you installed your self-compiled Qt to a separate
directory via 'make install'. You can fix this by either re-building your Qt
with the "-developer-build" configure option, or pass the include directory in
the source directory to qmake, e.g.


con's avatar
con committed
60 61
Third-party components
Kai Koehne's avatar
Kai Koehne committed
Qt Creator includes the following third-party components,
con's avatar
con committed
63 64 65 66 67 68
we thank the authors who made this possible:

* Open Source front-end for C++ (license MIT), enhanced for use in Qt Creator
  Roberto Raggi <>