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

Doc: Fix links to Boot2Qt topics

Browse Source 
And update information about Boot2Qt requirements.

Fixes: QTCREATORBUG-27251
Change-Id: Ifda686fafcd6b258a2c4dd8102260e05b637335d
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Nicholas Bennett <nicholas.bennett@qt.io>
This commit is contained in:
Leena Miettinen
2022-04-07 12:45:21 +02:00
parent ef52fa743b
commit 63aaa65439
8 changed files with 28 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -452,11 +452,10 @@
The Performance Analyzer can read Perf data files generated in either frame The Performance Analyzer can read Perf data files generated in either frame
pointer or dwarf mode. However, to generate the files correctly, numerous pointer or dwarf mode. However, to generate the files correctly, numerous
preconditions have to be met. All system images for the preconditions have to be met. All system images for the
\l{http://doc.qt.io/QtForDeviceCreation/qtee-supported-platforms.html} \l{https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html}
{Qt for Device Creation reference devices}, except for Freescale iMX53 Quick {Boot2Qt:Supported Target Devices and Development Hosts} are correctly set
Start Board and SILICA Architect Tibidabo, are correctly set up for up for profiling in the dwarf mode. For other devices, check whether Perf
profiling in the dwarf mode. For other devices, check whether Perf can read can read back its own data in a sensible way by checking the output of
back its own data in a sensible way by checking the output of
\c {perf report} or \c {perf script} for the recorded Perf data files. \c {perf report} or \c {perf script} for the recorded Perf data files.
\section1 Loading and Saving Trace Files \section1 Loading and Saving Trace Files

4
doc/qtcreator/src/linux-mobile/b2qtdev.qdoc
View File

@@ -63,8 +63,8 @@
\note On Ubuntu Linux, the development user account must have access to \note On Ubuntu Linux, the development user account must have access to
plugged in devices. To allow the development user access to the device plugged in devices. To allow the development user access to the device
via USB, create a new \c udev rule, as described in via USB, create a new \c udev rule, as described in
\l{https://doc.qt.io/QtForDeviceCreation/b2qt-requirements-x11.html#setting-up-usb-access-to-embedded-devices} \l{https://doc.qt.io/Boot2Qt/b2qt-requirements-x11.html#setting-up-usb-access-to-embedded-devices}
{Setting Up USB Access to Embedded Devices}. {Boot2Qt: Setting Up USB Access to Embedded Devices}.
You can edit the settings later in \uicontrol Tools > \uicontrol Options > You can edit the settings later in \uicontrol Tools > \uicontrol Options >
\uicontrol Devices > \uicontrol Devices. \uicontrol Devices > \uicontrol Devices.

12
doc/qtcreator/src/linux-mobile/creator-embedded-platforms.qdoc
View File

@@ -65,24 +65,22 @@
license holders, tooling is provided to customize the contents of the stack license holders, tooling is provided to customize the contents of the stack
as well as to take it into desired production hardware. as well as to take it into desired production hardware.
Either Windows 7 or later or Ubuntu Linux 64-bit 12.04 LTS Either Windows 10 64-bit or later or Ubuntu Linux 64-bit 20.04 LTS
or later is required to install and use Boot2Qt. or later is required to install and use Boot2Qt.
The following topics contain more information about developing applications The following topics contain more information about developing applications
for Boot2Qt devices: for Boot2Qt devices:
\list \list
\li \l{https://doc.qt.io/QtForDeviceCreation/qtee-supported-platforms.html} \li \l{https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html}
{Reference Target Devices and Development Hosts} {Boot2Qt: Supported Target Devices and Development Hosts}
\li \l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html} \li \l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
{Installation Guides} {Boot2Qt: Installation Guides}
\li \l{Connecting Boot2Qt Devices} \li \l{Connecting Boot2Qt Devices}
\li \l{Specifying Run Settings for Boot2Qt Devices} \li \l{Specifying Run Settings for Boot2Qt Devices}
\li \l{Deploying Applications to Boot2Qt Devices} \li \l{Deploying Applications to Boot2Qt Devices}
\li \l{https://doc.qt.io/qtcreator/creator-overview-qtasam.html} \li \l{https://doc.qt.io/qtcreator/creator-overview-qtasam.html}
{Qt Creator Plugin for Qt Application Manager} {Qt Creator Plugin for Qt Application Manager}
\li \l{https://doc.qt.io/QtForDeviceCreation/index.html}
{Qt for Device Creation}
\endlist \endlist
\section1 Generic Remote Linux \section1 Generic Remote Linux

6
doc/qtcreator/src/linux-mobile/creator-projects-settings-run-b2qt.qdocinc
View File

@@ -32,10 +32,8 @@
must create connections from the development host to the device and add the must create connections from the development host to the device and add the
device configurations to \l{glossary-buildandrun-kit}{kits}. Select device configurations to \l{glossary-buildandrun-kit}{kits}. Select
\uicontrol {Manage Kits} to add devices to kits. For more information, see \uicontrol {Manage Kits} to add devices to kits. For more information, see
the \l{http://doc.qt.io/QtForDeviceCreation/qtee-installation-guide.html} \l{http://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
{Installation Guide} in the {Boot2Qt: Installation Guide}.
\l{http://doc.qt.io/QtForDeviceCreation/index.html}{Qt for Device Creation}
documentation.
The run settings display the path to the executable file on the development The run settings display the path to the executable file on the development
host and on the device. host and on the device.

5
doc/qtcreator/src/overview/creator-only/creator-commercial-overview.qdoc
View File

@@ -40,9 +40,8 @@
\l{http://qt.io/licensing/}{Qt license}: \l{http://qt.io/licensing/}{Qt license}:
\list \list
\li \l{http://doc.qt.io/QtForDeviceCreation/index.html}{Developing for \li \l{https://doc.qt.io/Boot2Qt/index.html}{Boot2Qt}
embedded devices} \li \l{https://doc.qt.io/qtcreator/creator-overview-qtasam.html}
\li \l{http://doc.qt.io/qtcreator/creator-overview-qtasam.html}
{Qt Application Manager} integration {Qt Application Manager} integration
\endlist \endlist
*/ */

8
doc/qtcreator/src/projects/creator-only/creator-projects-build-run-tutorial.qdoc
View File

@@ -44,12 +44,10 @@
\l{Connecting Android Devices} and \l{Connecting iOS Devices}. \l{Connecting Android Devices} and \l{Connecting iOS Devices}.
To run an example application on a Boot2Qt device, you must set up To run an example application on a Boot2Qt device, you must set up
Qt for Device Creation on the development host and create connections Boot2Qt on the development host and create connections
between the host and devices. For more information, see between the host and devices. For more information, see
\l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html} \l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
{Installation Guides} in the {Boot2Qt: Installation Guides}
\l{http://doc.qt.io/QtForDeviceCreation/index.html}{Qt for Device Creation}
documentation.
If you have \l{Qt Design Studio Manual}{\QDS} installed, you can open If you have \l{Qt Design Studio Manual}{\QDS} installed, you can open
\QDS examples from \QC in \QDS. \QDS examples from \QC in \QDS.

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

@@ -49,7 +49,7 @@
\list \list
\li \l{Connecting Android Devices}{Android Device} \li \l{Connecting Android Devices}{Android Device}
\li \l{Connecting Bare Metal Devices}{Bare Metal Device} \li \l{Connecting Bare Metal Devices}{Bare Metal Device}
\li \l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html} \li \l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
{Boot2Qt Device} (commercial only) {Boot2Qt Device} (commercial only)
\li \l{Emulator}{Boot2Qt Emulator Device} (commercial only) \li \l{Emulator}{Boot2Qt Emulator Device} (commercial only)
\li \l{Connecting Generic Remote Linux Devices}{Generic Remote Linux Device} \li \l{Connecting Generic Remote Linux Devices}{Generic Remote Linux Device}

20
doc/qtcreator/src/qtquick/qtquick-live-preview-devices.qdoc
View File

@@ -81,19 +81,17 @@
\section2 Previewing on Boot2Qt Devices \section2 Previewing on Boot2Qt Devices
You can preview UIs on Boot2Qt devices that are supported by You can preview UIs on Boot2Qt devices. For a list of supported devices, see
\l{Qt for Device Creation}. For a list of supported devices, see \l{https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html}
\l{https://doc.qt.io/QtForDeviceCreation/qtdc-supported-platforms.html} {Boot2Qt: Supported Target Devices and Development Hosts}.
{Reference Target Devices and Development Hosts}.
You must configure the device as instructed in the You must configure the device as instructed in the
\l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html} \l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
{Installation Guides}. {Boot2Qt: Installation Guides}.
\note At the time of this writing, \macos is not supported as a development \note At the time of this writing, \macos is not supported as a development
host for Qt for Device Creation. This means that you cannot preview UIs on host for Boot2Qt. This means that you cannot preview UIs on
devices if you are using \QC on \macos. For more information about devices if you are using \QC on \macos. For more information, see
supported development hosts, see \l {https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html#supported-development-hosts}
\l {https://doc.qt.io/QtForDeviceCreation/qtdc-supported-platforms.html#supported-development-hosts} {Boot2Qt: Supported Development Hosts}.
{Supported Development Hosts}.
*/ */