feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

README: Update section about private headers

Browse Source 
It's not only QmlDesigner that nowadays uses private API.

Change-Id: I87ea88e780b3a8d7169d4c75e84dc4e78dd7cab7
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
This commit is contained in:
Kai Koehne
2013-04-18 11:19:54 +02:00
parent 53fb29bdda
commit c4be740bd6
1 changed files with 16 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
README
View File

@@ -37,27 +37,28 @@ Installation ("make install") is not needed. It is however possible, using
make install INSTALL_ROOT=$INSTALL_DIRECTORY make install INSTALL_ROOT=$INSTALL_DIRECTORY
Compiling Qt Quick Designer Private Header Dependencies
--------------------------- ---------------------------
Qt Quick Designer (QmlDesigner plugin) depends on "private" headers from Qt The Qt Quick Designer and the QNX plugin, and on Windows the Utils library,use
4.8.0, specifically from the QtDeclarative module. These private headers always private headers of Qt. These private headers always end with an "_p.h". Digia
end with an "_p.h". Digia does not promise to keep these files or APIs binary and the Qt Project do not promise to keep these files or APIs binary or source
or source compatible between releases. This means that when compiled, the compatible between releases. This means that when compiled, Qt Creator has a
plugin has a dependency to the exact Qt version it was compiled with. Running dependency to the exact Qt version it was compiled with. Running Qt Creator
Qt Creator with the plugin against updated Qt libraries (also for patch against updated Qt libraries (also for patch releases) might lead to link time
releases) might lead to link time failures, or even crashes. failures, or even crashes.
If you want to disable the plugin, you can pass "QT_PRIVATE_HEADERS=" to qmake: If you want to disable the plugins on Linux and Mac OS X, you can pass
"QT_PRIVATE_HEADERS=" to qmake:
qmake "QT_PRIVATE_HEADERS=" $SOURCE_DIRECTORY/qtcreator.pro qmake "QT_PRIVATE_HEADERS=" $SOURCE_DIRECTORY/qtcreator.pro
The plugin is not compiled if the private header files are not found. This The plugins are also automatically omitted if the private header files are
might be the case when you use a Qt version from your distribution, or not found. This might be the case when you use a Qt version from your
installed a self-compiled Qt to a separate directory via 'make install'. You distribution, or installed a self-compiled Qt to a separate directory via
can fix this by either re-building your Qt with the "-developer-build" 'make install'. You can fix this by either re-building your Qt with the
configure option, or by passing the include directory in the source directory "-developer-build" configure option, or by passing the include directory in
to qmake. For example: the source directory to qmake. For example:
qmake "QT_PRIVATE_HEADERS=$$QT_BUILD_TREE/include" $SOURCE_DIRECTORY/qtcreator.pro qmake "QT_PRIVATE_HEADERS=$$QT_BUILD_TREE/include" $SOURCE_DIRECTORY/qtcreator.pro