forked from qt-creator/qt-creator
dt
9bc9fe73e1
Reviewed-By: con Reviewed-By: Friedemann Kleint We now support renaming files. The version control system tries first to rename, if that doesn't support or can't rename the file we do a normal rename. (Note: git, hg, perforce > 2009.02 support renaming, cvs not. (perforce untested)). We correctly notify all editors of the renamed file and tell the project manager to rename the file in the project. Note: Only the qt4projectmanager knows how to rename files. Note: renaming folders, moving files to different folders, renaming .pro/.pri files is not supported. Those things can be later added after this has proven to work correctly in the simple case. Also we don't do any actions based on the renaming like renaming classes, changing include guards or #include lines.
Qt Creator 2.0.80 =============== Qt Creator is a crossplatform C++ IDE for development with the Qt framework. Supported Platforms =================== The binary packages support the following platforms: Windows XP SP2, Windows Vista (K)Ubuntu Linux 7.04 32bit and 64bit Mac OS 10.4 and later Building the sources requires Qt 4.7.0 or later. Compiling Qt Creator ==================== Prerequisites: * Qt 4.7 * On Windows: mingw 4.4 or later, Visual Studio 2008 or later * On Mac: XCode 2.5 or later We recommend that you build Qt Creator not in the source directory, but in a separate directory. To do that, use the following commands: mkdir $BUILD_DIRECTORY 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 ------------------------------------------------- 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: qmake "QT_PRIVATE_HEADERS=" $SOURCE_DIRECTORY/qtcreator.pro 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. qmake "QT_PRIVATE_HEADERS=$$QT_SOURCE_TREE/include" $SOURCE_DIRECTORY/qtcreator.pro Third-party components ====================== Qt Creator includes the following third-party components, we thank the authors who made this possible: * Open Source front-end for C++ (license MIT), enhanced for use in Qt Creator Roberto Raggi <roberto.raggi@gmail.com> QtCreator/src/shared/cplusplus