diff options
| author | Kai Koehne <kai.koehne@nokia.com> | 2010-12-08 09:05:44 +0100 |
|---|---|---|
| committer | con <qtc-committer@nokia.com> | 2010-12-08 10:25:16 +0100 |
| commit | c3212a53d21fb16877ecb2e04389e8109f76f5f9 (patch) | |
| tree | 6bde3071a295e76a7142984580745eddc862c8d2 /README | |
| parent | bff0dd4a16aaffd248cdaad576bb27faa6ec74b3 (diff) | |
| download | qt-creator-c3212a53d21fb16877ecb2e04389e8109f76f5f9.tar.gz | |
README: QmlJSInspector does not require private headers any more
QmlJSInspector does not depend on Qt private headers being available
any more: The needed private API files have been copied into the
QtCreator source repo.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 22 |
1 files changed, 11 insertions, 11 deletions
@@ -26,22 +26,22 @@ cd $BUILD_DIRECTORY qmake $SOURCE_DIRECTORY/qtcreator.pro make (or mingw32-make or nmake or jom, depending on your platform) -QmlDesigner, QmlInspector require private headers -------------------------------------------------- +QmlDesigner requires private headers from Qt 4.7.1 +-------------------------------------------------- -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. +The QmlDesigner plugin depends on "private" headers from Qt 4.7.1, 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 plugin has a dependency to the +exact Qt version it was compiled with. Running Qt Creator with the plugin 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: +If you want to disable the plugin, you can pass "QT_PRIVATE_HEADERS=" to qmake: qmake "QT_PRIVATE_HEADERS=" $SOURCE_DIRECTORY/qtcreator.pro -Anyhow, the plugins will not be compiled when the private header files needed +Anyhow, the plugin 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 |