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

Doc: don't use the term SDK in connection with Qt

Browse Source 
Replace with "Qt distributions" or "installers" or rewrite
in some other way.

Remove references to installing Qt 4 SDK, because it is
no longer available for downloading.

Change-Id: I291f82702e21d953f2efbb0e634d6454b4bc17b9
Reviewed-by: hjk <hjk121@nokiamail.com>
This commit is contained in:
Leena Miettinen
2014-03-14 16:02:01 +01:00
parent 2c42b06f00
commit 7b088afbe9
11 changed files with 32 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/howto/qtcreator-faq.qdoc
View File

@@ -105,7 +105,7 @@
\QC comes fully integrated with Qt documentation and examples using
the Qt Help plugin. The integrated Qt Reference Documentation is available
for Qt 4.4 and later. \QC, \QSDK, and other Qt deliverables contain
for Qt 4.4 and later. \QC and other Qt deliverables contain
documentation as .qch files. All the documentation is accessible in the
\gui Help mode.
@@ -121,9 +121,9 @@
\b {If I have a choice of GDB versions, which should I use?}
On Linux and Windows, use the Python-enabled GDB versions that are
installed when you install \QC and Qt SDK. On Mac OS X, use the GDB
provided with Xcode. For a custom target, you can build your own
Python-enabled GDB. Follow the instructions in
installed when you install \QC and \QSDK. On Mac OS X, GDB is no longer
officially supported. To build your own Python-enabled GDB, follow the
instructions in
\l{http://qt-project.org/wiki/QtCreatorBuildGdb}{Building GDB}.
You must use Python version 2.6 or 2.7.
@@ -161,11 +161,12 @@
many parallel processes as your CPU has cores. You can override this
behavior by using the \c{-j} parameter as described above.
\section1 Qt SDK Questions
\section1 Qt Installation Questions
\b {I cannot use QSslSocket with the SDK. What should I do?}
\b {I cannot use QSslSocket with the Qt I installed from binary packages.
What should I do?}
The Qt build in the SDK is built with QT_NO_OPENSSL defined. Rebuilding it
The Qt in the binary packages is built with QT_NO_OPENSSL defined. Rebuilding it
is possible. For more information, see
\l{http://www.qtcentre.org/threads/19222-Qssl}.