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

Doc: Polish creator-projects-compilers.qdoc

Browse Source 
Names have their own field in the UI now, no more need to double-click
in the table. Do some markup-cleanups while at it.

Change-Id: I7f456f8455a54c9ae05ffc8ab73aa8f8f6cc1e22
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
This commit is contained in:
Tobias Hunger
2015-07-01 12:48:38 +02:00
parent fdb04b5d00
commit 5eedc9d2f6
1 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/projects/creator-projects-compilers.qdoc
View File

@@ -74,17 +74,19 @@
\list 1
\li Select \uicontrol {Tools > Options > Build & Run > Compilers > Add} and
select a compiler in the list.
\li Select \uicontrol Tools > \uicontrol Options >
\uicontrol {Build & Run} > \uicontrol Compilers > \uicontrol Add
and select a compiler in the list.
\image qtcreator-toolchains.png
To clone the selected compiler, select \uicontrol {Clone}.
To clone the selected compiler, select \uicontrol Clone.
\li In the \uicontrol Name column, double-click the name to change it.
\li In the \uicontrol Name field, enter a name for the compiler to
identify it in \QC.
\li In the \uicontrol{Compiler path} field, enter the path to the directory
where the compiler is located.
\li In the \uicontrol {Compiler path} field, enter the path to the
directory where the compiler is located.
\li In the \uicontrol {Platform codegen flags} field, check the flags passed
to the compiler that specify the architecture on the target
@@ -96,6 +98,10 @@
The other settings to specify depend on the compiler.
\li In the \uicontrol ABI field, provide an identification for the
target architecture. This is used to warn about ABI mismatches
within the kits.
\endlist
\section1 Adding Custom Compilers
@@ -168,7 +174,7 @@
\section1 Troubleshooting MinGW Compilation Errors
If error messages displayed in the \uicontrol {Compile Output} pane contain
paths where slashes are missing (for example, C:QtSDK),
paths where slashes are missing (for example, \c {C:QtSDK}),
check your PATH variable. At the command line, enter the following commands:
\code