forked from qt-creator/qt-creator
1dc99e8ff3
use local8bit instead of latin1 resp. 8bit-passthrough, after all.
the situation was as follows:
- if the pro files and file names were all ascii, everything just worked
- if either contained non-ascii:
- on unix, the evaluator would work as long as the file content
encoding matched the file name encoding, and the ui would work as
long as the file name encoding was latin1 (i.e., on no modern
system)
- on windows, both would work only if the ansi code page was
latin1/cp1252 (i.e., on western systems)
i.e., even in the low-level evaluator, only native latin1 systems with
actual latin1 files worked consistently. given this situation, it makes
little sense to make an encoding adapter between the evaluator and the
ui as originally planned. instead, take the easy way out and use
local8bit - this continues to work for native latin1 systems+files in
the backend, and makes the ui work for everything the backend groks and
some more.
Reviewed-by: dt
Task-number: QTCREATORBUG-930
Qt Creator 1.3.86 =============== 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) Qml Support ----------- Define the QTCREATOR_WITH_QML environment variable to enable Qml support (before running qmake). 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