forked from qt-creator/qt-creator
Doc: Fix links to Boot2Qt topics
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
@@ -452,11 +452,10 @@
|
||||
The Performance Analyzer can read Perf data files generated in either frame
|
||||
pointer or dwarf mode. However, to generate the files correctly, numerous
|
||||
preconditions have to be met. All system images for the
|
||||
\l{http://doc.qt.io/QtForDeviceCreation/qtee-supported-platforms.html}
|
||||
{Qt for Device Creation reference devices}, except for Freescale iMX53 Quick
|
||||
Start Board and SILICA Architect Tibidabo, are correctly set up for
|
||||
profiling in the dwarf mode. For other devices, check whether Perf can read
|
||||
back its own data in a sensible way by checking the output of
|
||||
\l{https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html}
|
||||
{Boot2Qt:Supported Target Devices and Development Hosts} are correctly set
|
||||
up for profiling in the dwarf mode. For other devices, check whether Perf
|
||||
can read 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.
|
||||
|
||||
\section1 Loading and Saving Trace Files
|
||||
|
||||
@@ -63,8 +63,8 @@
|
||||
\note On Ubuntu Linux, the development user account must have access to
|
||||
plugged in devices. To allow the development user access to the device
|
||||
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}
|
||||
{Setting Up USB Access to Embedded Devices}.
|
||||
\l{https://doc.qt.io/Boot2Qt/b2qt-requirements-x11.html#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 >
|
||||
\uicontrol Devices > \uicontrol Devices.
|
||||
|
||||
@@ -65,24 +65,22 @@
|
||||
license holders, tooling is provided to customize the contents of the stack
|
||||
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.
|
||||
|
||||
The following topics contain more information about developing applications
|
||||
for Boot2Qt devices:
|
||||
|
||||
\list
|
||||
\li \l{https://doc.qt.io/QtForDeviceCreation/qtee-supported-platforms.html}
|
||||
{Reference Target Devices and Development Hosts}
|
||||
\li \l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html}
|
||||
{Installation Guides}
|
||||
\li \l{https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html}
|
||||
{Boot2Qt: Supported Target Devices and Development Hosts}
|
||||
\li \l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
|
||||
{Boot2Qt: Installation Guides}
|
||||
\li \l{Connecting Boot2Qt Devices}
|
||||
\li \l{Specifying Run Settings for Boot2Qt Devices}
|
||||
\li \l{Deploying Applications to Boot2Qt Devices}
|
||||
\li \l{https://doc.qt.io/qtcreator/creator-overview-qtasam.html}
|
||||
{Qt Creator Plugin for Qt Application Manager}
|
||||
\li \l{https://doc.qt.io/QtForDeviceCreation/index.html}
|
||||
{Qt for Device Creation}
|
||||
\endlist
|
||||
|
||||
\section1 Generic Remote Linux
|
||||
|
||||
@@ -32,10 +32,8 @@
|
||||
must create connections from the development host to the device and add the
|
||||
device configurations to \l{glossary-buildandrun-kit}{kits}. Select
|
||||
\uicontrol {Manage Kits} to add devices to kits. For more information, see
|
||||
the \l{http://doc.qt.io/QtForDeviceCreation/qtee-installation-guide.html}
|
||||
{Installation Guide} in the
|
||||
\l{http://doc.qt.io/QtForDeviceCreation/index.html}{Qt for Device Creation}
|
||||
documentation.
|
||||
\l{http://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
|
||||
{Boot2Qt: Installation Guide}.
|
||||
|
||||
The run settings display the path to the executable file on the development
|
||||
host and on the device.
|
||||
|
||||
@@ -40,9 +40,8 @@
|
||||
\l{http://qt.io/licensing/}{Qt license}:
|
||||
|
||||
\list
|
||||
\li \l{http://doc.qt.io/QtForDeviceCreation/index.html}{Developing for
|
||||
embedded devices}
|
||||
\li \l{http://doc.qt.io/qtcreator/creator-overview-qtasam.html}
|
||||
\li \l{https://doc.qt.io/Boot2Qt/index.html}{Boot2Qt}
|
||||
\li \l{https://doc.qt.io/qtcreator/creator-overview-qtasam.html}
|
||||
{Qt Application Manager} integration
|
||||
\endlist
|
||||
*/
|
||||
|
||||
@@ -44,12 +44,10 @@
|
||||
\l{Connecting Android Devices} and \l{Connecting iOS Devices}.
|
||||
|
||||
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
|
||||
\l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html}
|
||||
{Installation Guides} in the
|
||||
\l{http://doc.qt.io/QtForDeviceCreation/index.html}{Qt for Device Creation}
|
||||
documentation.
|
||||
\l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
|
||||
{Boot2Qt: Installation Guides}
|
||||
|
||||
If you have \l{Qt Design Studio Manual}{\QDS} installed, you can open
|
||||
\QDS examples from \QC in \QDS.
|
||||
|
||||
@@ -49,7 +49,7 @@
|
||||
\list
|
||||
\li \l{Connecting Android Devices}{Android 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)
|
||||
\li \l{Emulator}{Boot2Qt Emulator Device} (commercial only)
|
||||
\li \l{Connecting Generic Remote Linux Devices}{Generic Remote Linux Device}
|
||||
|
||||
@@ -81,19 +81,17 @@
|
||||
|
||||
\section2 Previewing on Boot2Qt Devices
|
||||
|
||||
You can preview UIs on Boot2Qt devices that are supported by
|
||||
\l{Qt for Device Creation}. For a list of supported devices, see
|
||||
\l{https://doc.qt.io/QtForDeviceCreation/qtdc-supported-platforms.html}
|
||||
{Reference Target Devices and Development Hosts}.
|
||||
You can preview UIs on Boot2Qt devices. For a list of supported devices, see
|
||||
\l{https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html}
|
||||
{Boot2Qt: Supported Target Devices and Development Hosts}.
|
||||
|
||||
You must configure the device as instructed in the
|
||||
\l{https://doc.qt.io/QtForDeviceCreation/b2qt-installation-guides.html}
|
||||
{Installation Guides}.
|
||||
\l{https://doc.qt.io/Boot2Qt/b2qt-installation-guides.html}
|
||||
{Boot2Qt: Installation Guides}.
|
||||
|
||||
\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
|
||||
devices if you are using \QC on \macos. For more information about
|
||||
supported development hosts, see
|
||||
\l {https://doc.qt.io/QtForDeviceCreation/qtdc-supported-platforms.html#supported-development-hosts}
|
||||
{Supported Development Hosts}.
|
||||
host for Boot2Qt. This means that you cannot preview UIs on
|
||||
devices if you are using \QC on \macos. For more information, see
|
||||
\l {https://doc.qt.io/Boot2Qt/qtdc-supported-platforms.html#supported-development-hosts}
|
||||
{Boot2Qt: Supported Development Hosts}.
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user