forked from qt-creator/qt-creator
Doc: Use \MinGW to prevent broken automatically generated links
Change-Id: Ib576e3be1035448905cc8c5bf23960450cf10057 Reviewed-by: Paul Wicking <paul.wicking@qt.io>
This commit is contained in:
@@ -100,7 +100,7 @@
|
||||
\li GCC, Clang
|
||||
\li LLDB, FSF GDB (experimental)
|
||||
\row
|
||||
\li Windows/MinGW
|
||||
\li Windows/\MinGW
|
||||
\li GCC
|
||||
\li GDB
|
||||
\row
|
||||
@@ -173,7 +173,7 @@
|
||||
\section2 GDB
|
||||
|
||||
On Windows, use the Python-enabled GDB version that is bundled
|
||||
with the Qt package or comes with recent versions of MinGW. On
|
||||
with the Qt package or comes with recent versions of \MinGW. On
|
||||
most Linux distributions, the GDB builds shipped with the system
|
||||
are sufficient.
|
||||
|
||||
|
@@ -136,7 +136,7 @@
|
||||
In general, \key F5 and the \uicontrol {Start Debugging of Startup Project}
|
||||
button are set up in a
|
||||
way to start the operating mode that is commonly used in a given context. So
|
||||
if the current project is set up as a C++ application using the MinGW
|
||||
if the current project is set up as a C++ application using the \MinGW
|
||||
toolchain targeting desktop Windows, the GDB engine will be started in Start
|
||||
Internal mode. If the current project is a QML application using C++
|
||||
plugins, a "mixed" QML/C++ engine will be started, with the C++ parts being
|
||||
|
@@ -46,7 +46,7 @@
|
||||
For more information about where the files are located on each supported
|
||||
platform, see \l {Location of Settings Files}.
|
||||
|
||||
\b {\QC comes with MinGW, should I use this version with Qt?}
|
||||
\b {\QC comes with \MinGW, should I use this version with Qt?}
|
||||
|
||||
Use the version that was built against the Qt version.
|
||||
|
||||
|
@@ -57,9 +57,9 @@
|
||||
\li GNU Compiler Collection (GCC) is a compiler for Linux and
|
||||
\macos.
|
||||
|
||||
\li MinGW (Minimalist GNU for Windows) is a native software port of GCC
|
||||
\li \MinGW (Minimalist GNU for Windows) is a native software port of GCC
|
||||
and GNU Binutils for use in the development of native Microsoft
|
||||
Windows applications on Windows. MinGW is
|
||||
Windows applications on Windows. \MinGW is
|
||||
distributed together with \QC and Qt installers for Windows.
|
||||
|
||||
\li ICC (Intel C++ Compiler) is a group of C and C++ compilers.
|
||||
@@ -114,7 +114,7 @@
|
||||
|
||||
\section1 Specifying Compiler Settings
|
||||
|
||||
To build an application using GCC, MinGW, Clang, or QCC, specify the path
|
||||
To build an application using GCC, \MinGW, Clang, or QCC, specify the path
|
||||
to the directory where the compiler is located and select
|
||||
the application binary interface (ABI) version from the list of available
|
||||
versions. You can also create a custom ABI definition.
|
||||
@@ -215,7 +215,7 @@
|
||||
see \l{Using Custom Output Parsers}.
|
||||
\endlist
|
||||
|
||||
\section1 Troubleshooting MinGW Compilation Errors
|
||||
\section1 Troubleshooting \MinGW Compilation Errors
|
||||
|
||||
If error messages displayed in the \uicontrol {Compile Output} pane contain
|
||||
paths where slashes are missing (for example, \c {C:QtSDK}),
|
||||
@@ -228,7 +228,7 @@
|
||||
\endcode
|
||||
|
||||
If these commands show paths, they have been added to the global PATH
|
||||
variable during the installation of a tool chain based on Cygwin or MinGW,
|
||||
variable during the installation of a tool chain based on Cygwin or \MinGW,
|
||||
even though this is against Windows conventions.
|
||||
|
||||
To keep working with the third-party tool chain, create a new shell link
|
||||
|
@@ -52,7 +52,7 @@
|
||||
|
||||
\list
|
||||
\li Qt for WebAssembly 5.13.1, or later
|
||||
\li On Windows: \l{http://wiki.qt.io/MinGW}{MinGW} 7.3.0, or later
|
||||
\li On Windows: \l{http://wiki.qt.io/MinGW}{\MinGW} 7.3.0, or later
|
||||
\li \l{https://emscripten.org/docs/introducing_emscripten/index.html}
|
||||
{emscripten} tool chain for compiling to WebAssembly
|
||||
\li \c sed stream editor
|
||||
|
@@ -137,7 +137,7 @@
|
||||
|
||||
The \QC that is included in pre-built Qt packages on Windows is built with
|
||||
the Microsoft Visual Studio compiler, whereas the version of Qt shipped for
|
||||
building applications is configured and built to use the MinGW/g++ compiler.
|
||||
building applications is configured and built to use the \MinGW/g++ compiler.
|
||||
Plugins built by using this version of Qt cannot be loaded by \QC because
|
||||
the build-keys do not match. The plugins can only be used in the standalone
|
||||
version of \QD. Choose \uicontrol Help > \uicontrol {About \QC} to check the
|
||||
@@ -145,7 +145,7 @@
|
||||
|
||||
To use \QD plugins that were built for the shipped Qt version, make sure
|
||||
that \QC is built with the same compiler by either recompiling \QC using
|
||||
MinGW or recompiling Qt with Microsoft Visual Studio, depending on which
|
||||
\MinGW or recompiling Qt with Microsoft Visual Studio, depending on which
|
||||
configuration you want to use for your applications.
|
||||
|
||||
*/
|
||||
|
Reference in New Issue
Block a user