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

Doc: Write "toolchain" as one word

Browse Source 
We still have some occurrences in the UI where it is written as
two words, though.

Change-Id: I245e4185c8ede4313bbe64641f38a3850fa8cbeb
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
Leena Miettinen
2024-05-07 11:16:57 +02:00
parent f9b097436b
commit 1218175c78
13 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/qtcreator/src/analyze/cpu-usage-analyzer.qdoc
View File

@@ -456,7 +456,7 @@
\uicontrol {Performance Analyzer Options}. This format is self-contained, and
therefore loading it does not require you to specify the recording
environment. You can transfer such trace files to a different computer
without any tool chain or debug symbols and analyze them there.
without any toolchain or debug symbols and analyze them there.
\section1 Troubleshooting

2
doc/qtcreator/src/analyze/creator-analyze.qdoc
View File

@@ -65,7 +65,7 @@
\section1 Checking Code Coverage
Install the \l{https://doc.qt.io/coco/}{Coco} code coverage tool chain for
Install the \l{https://doc.qt.io/coco/}{Coco} code coverage toolchain for
Tcl, QML, C# and C/C++ programs on \macOS, Linux, or Windows to analyze the
way an application runs as part of a test suite, for example. Use the
results to make the tests more efficient and complete.

4
doc/qtcreator/src/android/androiddev.qdoc
View File

@@ -56,7 +56,7 @@
\QC offers to automatically install all the necessary packages and tools and
to set up your \l{Qt for Android} development environment by creating
debuggers, tool chains, and kits.
debuggers, toolchains, and kits.
Use \QC to:
@@ -184,7 +184,7 @@
\section1 Add NDK paths
To add custom NDK paths manually to the global list of NDKs, select
\uicontrol Add. This creates custom tool chains and debuggers associated
\uicontrol Add. This creates custom toolchains and debuggers associated
to that NDK.
You have to manually create a kit that uses the custom NDK.

6
doc/qtcreator/src/baremetal/creator-baremetal-dev.qdoc
View File

@@ -9,7 +9,7 @@
\title Developing for Bare Metal Devices
\brief Create kits to use Bare Metal tool chains installed on the computer
\brief Create kits to use Bare Metal toolchains installed on the computer
to build applications for and run and debug them on connected Bare Metal
devices.
@@ -18,14 +18,14 @@
\note Enable the Bare Metal plugin to use it.
Install Bare Metal tool chains on the computer to build applications for
Install Bare Metal toolchains on the computer to build applications for
Bare Metal devices. Connect the devices to the computer to run and debug
applications on them.
\note If you use qmake to build the project and the device does not have
Qt libraries, you need a fake Qt installation.
The following tool chains are supported for building applications:
The following toolchains are supported for building applications:
\list
\li GCC: Microchip Technology (AVR, AVR32, PIC16, PIC32),

2
doc/qtcreator/src/debugger/creator-only/creator-debugger-setup.qdoc
View File

@@ -20,7 +20,7 @@
\QC supports native debuggers for debugging compiled code.
On most supported platforms, you can use the GNU Symbolic Debugger (GDB).
On Microsoft Windows, when using the Microsoft tool chain, you need the
On Microsoft Windows, when using the Microsoft toolchain, you need the
Microsoft Console Debugger (CDB). On \macos and Linux, you can use the LLDB
debugger.

2
doc/qtcreator/src/debugger/creator-only/creator-debugger.qdoc
View File

@@ -438,7 +438,7 @@
used for building the binary for which the core file was created.
If the core file stems from a binary not built by \QC or a process
not initiated by \QC, select a kit that matches the setup used as
closely as possible, in respect to the specified device, tool chain,
closely as possible, in respect to the specified device, toolchain,
debugger, and sysroot.
\li In \uicontrol {Core file}, specify the core file to inspect.
\li In \uicontrol {Executable of symbol file}, specify

2
doc/qtcreator/src/howto/creator-external-tools.qdoc
View File

@@ -77,7 +77,7 @@
{build environment} or \l {Specify the run environment}
{run environment} of the active project. Select the build or run
environment if the system environment does not have the necessary
PATH settings to find the tool chain, for example.
PATH settings to find the toolchain, for example.
\else
\li In the \uicontrol {Base environment} field, use the default settings.
\endif

2
doc/qtcreator/src/ios/creator-ios-dev.qdoc
View File

@@ -12,7 +12,7 @@
\brief Connect iOS devices to your local machine with a USB cable to
run applications on them.
After you install Xcode, \QC automatically detects the tool chain and creates
After you install Xcode, \QC automatically detects the toolchain and creates
the necessary \l{Kits}{kits} to build applications for and run them on
configured iOS devices.

2
doc/qtcreator/src/overview/creator-only/creator-glossary.qdoc
View File

@@ -77,7 +77,7 @@
\li \QC groups build and run specific settings as kits to make
cross-platform development easier. Each kit consists of a set
of values that define one environment, such as a \e {device},
tool chain, Qt version, and debugger command to use. Configure kits at
toolchain, Qt version, and debugger command to use. Configure kits at
\preferences > \uicontrol Kits.
\row

12
doc/qtcreator/src/projects/creator-only/creator-projects-compilers.qdoc
View File

@@ -103,7 +103,7 @@
\li Other than the listed compilers and remote compilers.
\endtable
The emscripten compiler is tool chain for compiling to
The emscripten compiler is toolchain for compiling to
\l{Building Applications for the Web}{WebAssembly}.
\section2 Bare-metal compilers
@@ -145,10 +145,10 @@
\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 toolchain 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
To keep working with the third-party toolchain, create a new shell link
that adds the required paths (as Visual Studio and Qt do). The shell link
must point to cmd.exe:
@@ -157,16 +157,16 @@
where the /K parameter carries out the command specified in the bat file.
Create the myenv.bat file at \e path_to, which should be in a convenient
location. In the file, specify the paths to the tool chains. For example,
location. In the file, specify the paths to the toolchains. For example,
\c {set PATH=C:\path1;C:\path2;%PATH%}
where \e path1 and \e path2 are paths to the tool chains.
where \e path1 and \e path2 are paths to the toolchains.
Finally, remove the paths from the global PATH, reboot the computer, and
run the \c where commands again to verify that the global PATH is now clean.
You can use the shell link to run the tools in the third-party tool chains.
You can use the shell link to run the tools in the third-party toolchains.
\sa {Compilers}, {Add Nim compilers}, {Add custom compilers},
{Developing for Bare Metal Devices}, {Supported Platforms}

2
doc/qtcreator/src/qnx/creator-projects-how-to-run-qnx.qdoc
View File

@@ -18,7 +18,7 @@
\li Select \inlineimage icons/run_small.png (\uicontrol Run).
\endlist
\QC uses the compiler specified in the QNX tool chain to build the
\QC uses the compiler specified in the QNX toolchain to build the
application.
\note Debugging is currently only fully supported on Linux and \macos.

6
doc/qtcreator/src/webassembly/creator-webassembly.qdoc
View File

@@ -24,7 +24,7 @@
\note Enable the WebAssembly plugin to use it.
To build applications for the web and run them in a web browser, you need to
install Qt for WebAssembly and the tool chain for compiling to WebAssembly.
install Qt for WebAssembly and the toolchain for compiling to WebAssembly.
\section1 Requirements
@@ -35,12 +35,12 @@
\li Qt for WebAssembly 5.15, 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
{emscripten} toolchain for compiling to WebAssembly
\endlist
\section1 Setting Up the Development Environment
You need to install and configure Qt for WebAssembly and the tool chain for
You need to install and configure Qt for WebAssembly and the toolchain for
compiling to WebAssembly. \QOI automatically adds a build and
run kit to \QC.

2
doc/qtcreatordev/src/qtcreator-dev.qdoc
View File

@@ -138,7 +138,7 @@
Most software projects and development processes require various external
tools. Several external tools, such as popular version control systems and
build tool chains are integrated into \QC. However, it is impossible for a
build toolchains are integrated into \QC. However, it is impossible for a
single tool to cover all the use cases, and therefore you can integrate
additional tools to \QC.