Doc: Use "remote Linux" instead of "generic remote Linux"

- Reflect the term changes in the UI.
- Move info about SSH port property to the wizard step list.
- Make the topic names in "Deploying to Devices" shorter.
- Remove some unnecessary "if defined(qtdesignstudio)" conditions
  from topics that are not used in the QDS Manual.

Task-number: QTCREATORBUG-27876
Change-Id: I2282257f245c31af82a41ea0e533407bf1cbd775
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Nicholas Bennett <nicholas.bennett@qt.io>
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2022-10-27 16:21:22 +02:00
parent c4ee485bdf
commit 65cfbc1b6e
27 changed files with 81 additions and 98 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.2 KiB

View File

@@ -216,7 +216,7 @@
To start an AVD, select \uicontrol {Start AVD}. Usually, you don't need to To start an AVD, select \uicontrol {Start AVD}. Usually, you don't need to
start AVDs separately because they are automatically started when you start AVDs separately because they are automatically started when you
select them in the \l{Building for Multiple Platforms}{kit selector} to select them in the \l{Building for Multiple Platforms}{kit selector} to
\l{Deploying Applications to Android Devices}{deploy applications} to them. \l{Deploying to Android}{deploy applications} to them.
To remove an AVD from the list and the kit selector, select To remove an AVD from the list and the kit selector, select
\uicontrol {Erase AVD}. \uicontrol {Erase AVD}.

View File

@@ -6,7 +6,7 @@
\page creator-deploying-android.html \page creator-deploying-android.html
\nextpage creator-deployment-b2qt.html \nextpage creator-deployment-b2qt.html
\title Deploying Applications to Android Devices \title Deploying to Android
On Android, applications are distributed in specially structured types of On Android, applications are distributed in specially structured types of
ZIP packages called Application Packages (APK) or Android App Bundles (AAB). ZIP packages called Application Packages (APK) or Android App Bundles (AAB).

View File

@@ -176,6 +176,6 @@
\li \l {Opening Projects} \li \l {Opening Projects}
\li \l {CMake Build Configuration} \li \l {CMake Build Configuration}
\li \l {Specifying Run Settings} \li \l {Specifying Run Settings}
\li \l {Deploying Applications to Generic Remote Linux Devices} \li \l {Deploying to Remote Linux}
\endlist \endlist
*/ */

View File

@@ -4,7 +4,7 @@
/*! /*!
\page creator-adding-docker-devices.html \page creator-adding-docker-devices.html
\previouspage creator-developing-b2qt.html \previouspage creator-developing-b2qt.html
\nextpage creator-developing-generic-linux.html \nextpage creator-developing-ios.html
\title Adding Docker Devices \title Adding Docker Devices

View File

@@ -2,7 +2,7 @@
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only // SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
/*! /*!
\previouspage creator-developing-generic-linux.html \previouspage creator-adding-docker-devices.html
\page creator-developing-ios.html \page creator-developing-ios.html
\nextpage creator-developing-mcu.html \nextpage creator-developing-mcu.html

View File

@@ -4,9 +4,9 @@
/*! /*!
\page creator-deployment-b2qt.html \page creator-deployment-b2qt.html
\previouspage creator-deploying-android.html \previouspage creator-deploying-android.html
\nextpage creator-deployment-embedded-linux.html \nextpage creator-deployment-qnx.html
\title Deploying Applications to Boot2Qt Devices \title Deploying to Boot2Qt
You can specify settings for deploying applications to \l{Boot2Qt} devices You can specify settings for deploying applications to \l{Boot2Qt} devices
in the project configuration file and in \uicontrol Projects > in the project configuration file and in \uicontrol Projects >
@@ -15,7 +15,7 @@
\image qtcreator-boot2qt-deployment-steps.png "Boot2Qt deployment steps" \image qtcreator-boot2qt-deployment-steps.png "Boot2Qt deployment steps"
The deployment process is described in more detail in The deployment process is described in more detail in
\l{Deploying Applications to Generic Remote Linux Devices}. \l{Deploying to Remote Linux}.
\section1 Launching Applications on Boot \section1 Launching Applications on Boot

View File

@@ -9,20 +9,16 @@
/*! /*!
\page creator-deployment-embedded-linux.html \page creator-deployment-embedded-linux.html
\previouspage creator-deployment-b2qt.html \previouspage creator-deployment-qnx.html
\if defined(qtdesignstudio)
\nextpage creator-connecting-mobile.html \nextpage creator-connecting-mobile.html
\else
\nextpage creator-deployment-qnx.html
\endif
\title Deploying Applications to Generic Remote Linux Devices \title Deploying to Remote Linux
You can specify settings for deploying applications to generic remote You can specify settings for deploying applications to generic remote
Linux devices in the project configuration file and in the Linux devices in the project configuration file and in the
\uicontrol Projects mode, in \uicontrol {Run Settings}. \uicontrol Projects mode, in \uicontrol {Run Settings}.
\image qtcreator-embedded-linux-deployment-details.png "Deploy to embedded Linux" \image qtcreator-embedded-linux-deployment-details.png "Deploy to remote Linux devices"
The files to be installed are listed in the \uicontrol {Deployment} step, The files to be installed are listed in the \uicontrol {Deployment} step,
the \uicontrol {Files to deploy} field. The \uicontrol {Source File Path} the \uicontrol {Files to deploy} field. The \uicontrol {Source File Path}

View File

@@ -13,7 +13,7 @@
\list \list
\li \l {Bare Metal} \li \l {Bare Metal}
\li \l {Boot2Qt} \li \l {Boot2Qt}
\li \l {Generic Remote Linux} \li \l {Remote Linux}
\li \l {Microcontroller Units (MCU)} \li \l {Microcontroller Units (MCU)}
\li \l QNX \li \l QNX
\endlist \endlist
@@ -31,7 +31,7 @@
\section1 Bare Metal \section1 Bare Metal
You can run and debug applications on small devices that are not supported You can run and debug applications on small devices that are not supported
by the generic remote Linux device plugin by using GDB or a hardware by the remote Linux device plugin by using GDB or a hardware
debugger. debugger.
For more information about developing applications for Bare Metal devices, For more information about developing applications for Bare Metal devices,
@@ -56,24 +56,24 @@
{Boot2Qt: 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 to Boot2Qt}
\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}
\endlist \endlist
\section1 Generic Remote Linux \section1 Remote Linux
You must have a tool chain for building applications for embedded Linux You must have a tool chain for building applications for embedded Linux
devices installed on the development PC. devices installed on the development PC.
The following topics contain more information about developing applications The following topics contain more information about developing applications
for generic remote Linux devices: for remote Linux devices:
\list \list
\li \l{Connecting Generic Remote Linux Devices} \li \l{Connecting Remote Linux Devices}
\li \l{Deploying Applications to Generic Remote Linux Devices} \li \l{Deploying to Remote Linux}
\li \l{Specifying Run Settings for Linux-Based Devices} \li \l{Specifying Run Settings for Linux-Based Devices}
\li \l{Running on Generic Remote Linux Devices} \li \l{Running on Remote Linux 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}
\endlist \endlist
@@ -105,7 +105,7 @@
\list \list
\li \l{Connecting QNX Devices} \li \l{Connecting QNX Devices}
\li \l{Deploying Applications to QNX Neutrino Devices} \li \l{Deploying to QNX Neutrino}
\li \l{Specifying Run Settings for QNX Devices} \li \l{Specifying Run Settings for QNX Devices}
\li \l{Running on QNX Devices} \li \l{Running on QNX Devices}
\li \l{Qt for QNX} \li \l{Qt for QNX}

View File

@@ -4,14 +4,14 @@
/*! /*!
//! [running on embedded linux] //! [running on embedded linux]
\section1 Running on Generic Remote Linux Devices \section1 Running on Remote Linux Devices
To build the application and run it on a device: To build the application and run it on a device:
\list 1 \list 1
\li Specify a connection to the device. For more information, see \li Specify a connection to the device. For more information, see
\l{Connecting Generic Remote Linux Devices}. \l{Connecting Remote Linux Devices}.
\li Click the \uicontrol Run button. \li Click the \uicontrol Run button.
@@ -25,12 +25,10 @@
displayed on the device. Command-line output is visible in the \QC displayed on the device. Command-line output is visible in the \QC
\uicontrol {Application Output} view. \uicontrol {Application Output} view.
Choose \uicontrol {Projects > Embedded Linux > Run} to view the settings for deploying In the \uicontrol {Projects} mode, select the remote Linux kit and then
the application to the connected device. select \uicontrol {Run} to view the settings for deploying the application
\if defined(qtcreator) to the connected device. For more information, see
For more information, see
\l{Specifying Run Settings for Linux-Based Devices}. \l{Specifying Run Settings for Linux-Based Devices}.
\endif
Debugging works transparently if GDB server is installed on the device and Debugging works transparently if GDB server is installed on the device and
it is compatible with the GDB on the host. it is compatible with the GDB on the host.

View File

@@ -17,7 +17,7 @@
host and on the device. host and on the device.
For more information on the deployment steps, see For more information on the deployment steps, see
\l{Deploying Applications to Boot2Qt Devices}. \l{Deploying to Boot2Qt}.
//! [run settings boot2qt] //! [run settings boot2qt]
*/ */

View File

@@ -11,7 +11,7 @@
host to the device and add the device configurations to host to the device and add the device configurations to
\l{glossary-buildandrun-kit}{kits}. Click \uicontrol {Manage Kits} to add devices \l{glossary-buildandrun-kit}{kits}. Click \uicontrol {Manage Kits} to add devices
to kits. For more information, see to kits. For more information, see
\l {Connecting Generic Remote Linux Devices}. \l {Connecting Remote Linux Devices}.
When you run the application, \QC copies the files to the connected device. When you run the application, \QC copies the files to the connected device.

View File

@@ -3,15 +3,10 @@
/*! /*!
\page creator-developing-generic-linux.html \page creator-developing-generic-linux.html
\if defined(qtdesignstudio) \previouspage creator-developing-qnx.html
\previouspage creator-developing-android.html \nextpage creator-setup-webassembly.html
\nextpage studio-advanced.html
\else
\previouspage creator-adding-docker-devices.html
\nextpage creator-developing-ios.html
\endif
\title Connecting Generic Remote Linux Devices \title Connecting Remote Linux Devices
You can connect generic Linux devices to the development PC to run, You can connect generic Linux devices to the development PC to run,
debug, and analyze applications built for them from \QC. debug, and analyze applications built for them from \QC.
@@ -19,10 +14,10 @@
If you have a tool chain for building applications for embedded Linux If you have a tool chain for building applications for embedded Linux
devices installed on the development PC, you can add devices installed on the development PC, you can add
it to \QC. You can then select a \l{glossary-buildandrun-kit}{kit} it to \QC. You can then select a \l{glossary-buildandrun-kit}{kit}
with \uicontrol {Embedded Linux} device type to with the device type \uicontrol {Remote Linux Device} to
build applications for and run them on the devices. build applications for and run them on the devices.
To be able to run and debug applications on generic remote Linux devices, To be able to run and debug applications on remote Linux devices,
you must add devices and select them in the \QC \l{glossary-buildandrun-kit} you must add devices and select them in the \QC \l{glossary-buildandrun-kit}
{kit}. {kit}.
@@ -30,7 +25,7 @@
in \uicontrol Edit > \uicontrol Preferences > \uicontrol Devices > in \uicontrol Edit > \uicontrol Preferences > \uicontrol Devices >
\uicontrol Devices. \uicontrol Devices.
\image qtcreator-linux-device-configurations.png "Devices dialog" \image qtcreator-preferences-devices-remote-linux.webp "Remote Linux Device in the Devices tab"
You can protect the connections between \QC and a device by using an You can protect the connections between \QC and a device by using an
\l{https://www.openssh.com/}{OpenSSH} connection. OpenSSH is a \l{https://www.openssh.com/}{OpenSSH} connection. OpenSSH is a
@@ -47,7 +42,7 @@
you may need to enter the password on every connection to the device, you may need to enter the password on every connection to the device,
or, if caching is enabled, at every \QC restart. or, if caching is enabled, at every \QC restart.
To configure connections between \QC and an embedded Linux device and to To configure connections between \QC and a remote Linux device and to
specify build and run settings for the device: specify build and run settings for the device:
\list 1 \list 1
@@ -69,19 +64,22 @@
\li Select \uicontrol Edit > \uicontrol Preferences > \li Select \uicontrol Edit > \uicontrol Preferences >
\uicontrol Devices > \uicontrol Devices > \uicontrol Add > \uicontrol Devices > \uicontrol Devices > \uicontrol Add >
\uicontrol {Generic Linux Device} \uicontrol {Remote Linux Device}
> \uicontrol {Start Wizard}. > \uicontrol {Start Wizard}.
\image qtcreator-screenshot-devconf-linux.png "Connection Data wizard" \image qtcreator-preferences-devices-remote-linux-connection.webp "Connection Data wizard"
\li In the \uicontrol {The name to identify this configuration} field, \li In \uicontrol {The name to identify this configuration},
enter a name for the connection. enter a name for the connection.
\li In the \uicontrol {The device's host name or IP address} field, \li In \uicontrol {The device's host name or IP address},
enter the host name or IP address of the device. enter the host name or IP address of the device.
This value will be available in the variable \c %{Device:HostAddress}. This value will be available in the variable \c %{Device:HostAddress}.
\li In the \uicontrol {The username to log into the device} field, \li In \uicontrol {The device's SSH port number}, enter the port
number to use for SSH connections. This value will be
available in the variable \c %{Device:SshPort}.
\li In \uicontrol {The username to log into the device},
enter the username to log into the device and run the enter the username to log into the device and run the
application as. application as.
This value will be available in the variable \c %{Device:UserName}. This value will be available in the variable \c %{Device:UserName}.
@@ -89,7 +87,7 @@
\li Select \uicontrol {Next} to open the \li Select \uicontrol {Next} to open the
\uicontrol {Key Deployment} dialog. \uicontrol {Key Deployment} dialog.
\image qtcreator-generic-linux-device-key-deployment.png "Key Deployment dialog" \image qtcreator-preferences-devices-remote-linux-key-deployment.webp "Key Deployment dialog"
\li In \uicontrol {Private key file}, select a private key file \li In \uicontrol {Private key file}, select a private key file
to use for authentication. This value will be available in to use for authentication. This value will be available in
@@ -107,14 +105,16 @@
\endlist \endlist
All of these parameters can be edited later, as well as additional ones that the All of these parameters can be edited later, as well as additional ones that the
wizard does not show because there are sensible default values. One of these is wizard does not show because there are sensible default values.
the SSH port number, which is available in the variable \c %{Device:SshPort}.
\li Select \uicontrol Edit > \uicontrol Preferences > \uicontrol Kits > \li Select \uicontrol Edit > \uicontrol Preferences > \uicontrol Kits >
\uicontrol Add to add a kit for building for the device. Select the \uicontrol Add to add a kit for building for the device. Select the
Qt version, compiler, and device that you added above, and choose Qt version, compiler, and device that you added above, and select
\uicontrol {Generic Linux Device} for the device type. \uicontrol {Remote Linux Device} in \uicontrol {Device type}.
To build on the remote device, select \uicontrol {Remote Linux Device}
also in \uicontrol {Build device}.
\li To specify build settings: \li To specify build settings:
@@ -133,7 +133,7 @@
When you run the project, \QC deploys the application as specified by the When you run the project, \QC deploys the application as specified by the
deploy steps. By default, \QC copies the application files to the device. deploy steps. By default, \QC copies the application files to the device.
For more information, see \l{Deploying Applications to Generic Remote Linux Devices}. For more information, see \l{Deploying to Remote Linux}.
\endlist \endlist

View File

@@ -22,31 +22,28 @@
\list \list
\li \l{Deploying Applications to Android Devices} \li \l{Deploying to Android}
When you deploy the application to an Android device, \QC copies When you deploy the application to an Android device, \QC copies
the application files to the device. In addition, you can determine the application files to the device. In addition, you can determine
the Qt libraries to use. the Qt libraries to use.
\li \l {Deploying Applications to Boot2Qt Devices} \li \l {Deploying to Boot2Qt}
When you deploy the application to a Boot2Qt device, \QC copies When you deploy the application to a Boot2Qt device, \QC copies
the application files to the connected device. You can then test the application files to the connected device. You can then test
and debug the application on the device with \QC. and debug the application on the device with \QC.
\li \l{Deploying Applications to Generic Remote Linux Devices} \li \l{Deploying to QNX Neutrino}
When you deploy the application to a generic Linux-based device, \QC
copies the application files to the connected device. You can then
test and debug the application on the device with \QC.
\if defined(qtcreator)
\li \l{Deploying Applications to QNX Neutrino Devices}
When you deploy the application to a QNX Neutrino device, \QC copies When you deploy the application to a QNX Neutrino device, \QC copies
the application files to the connected device. You can then test and the application files to the connected device. You can then test and
debug the application on the device with \QC. debug the application on the device with \QC.
\endif
\li \l{Deploying to Remote Linux}
When you deploy the application to a generic Linux-based device, \QC
copies the application files to the connected device. You can then
test and debug the application on the device with \QC.
\endlist \endlist
*/ */

View File

@@ -36,7 +36,7 @@
\list \list
\li \l{Connecting Android Devices} \li \l{Connecting Android Devices}
\li \l{Deploying Applications to Android Devices} \li \l{Deploying to Android}
\li \l{Running on Multiple Platforms} \li \l{Running on Multiple Platforms}
\li \l{Creating a Mobile Application} \li \l{Creating a Mobile Application}
\li \l{Debugging on Android Devices} \li \l{Debugging on Android Devices}

View File

@@ -9,7 +9,7 @@
/*! /*!
\page creator-connecting-mobile.html \page creator-connecting-mobile.html
\previouspage creator-deployment-qnx.html \previouspage creator-deployment-embedded-linux.html
\nextpage creator-developing-android.html \nextpage creator-developing-android.html
\title Connecting Devices \title Connecting Devices
@@ -40,32 +40,21 @@
Qt version targeting Android and the Android SDK and NDK to develop Qt version targeting Android and the Android SDK and NDK to develop
for Android devices. for Android devices.
\if defined(qtcreator)
\li \l{Connecting Bare Metal Devices} \li \l{Connecting Bare Metal Devices}
You can connect bare metal devices to the development PC and use \QC You can connect bare metal devices to the development PC and use \QC
to debug applications on them with GDB or a hardware debugger. to debug applications on them with GDB or a hardware debugger.
\endif
\li \l{Connecting Boot2Qt Devices} \li \l{Connecting Boot2Qt Devices}
You can connect \l{Boot2Qt} devices to the development PC to run, You can connect \l{Boot2Qt} devices to the development PC to run,
debug, and analyze applications built for them from \QC. debug, and analyze applications built for them from \QC.
\if defined(qtcreator)
\li \l {Adding Docker Devices} \li \l {Adding Docker Devices}
You can add Docker images as \e devices to run, debug, and analyze You can add Docker images as \e devices to run, debug, and analyze
applications built for Docker containers from \QC. applications built for Docker containers from \QC.
\endif
\li \l{Connecting Generic Remote Linux Devices}
If you have a tool chain for building applications for embedded
Linux devices installed on the development
PC, you can add it and the device to \QC.
\if defined(qtcreator)
\li \l{Connecting iOS Devices} \li \l{Connecting iOS Devices}
You use the tools delivered with Xcode to connect devices to \QC. You use the tools delivered with Xcode to connect devices to \QC.
@@ -83,11 +72,15 @@
debug applications on them from within \QC. This is currently only debug applications on them from within \QC. This is currently only
supported for QNX Neutrino devices, and requires the QNX SDK to be supported for QNX Neutrino devices, and requires the QNX SDK to be
installed on the development PC. installed on the development PC.
\endif
\li \l{Connecting Remote Linux Devices}
If you have a tool chain for building applications for embedded
Linux devices installed on the development
PC, you can add it and the device to \QC.
\endlist \endlist
\if defined(qtcreator)
\section1 Related Topics \section1 Related Topics
\list \list
@@ -106,5 +99,4 @@
local Linux PC, remote generic SSH Linux targets, or local Linux PC, remote generic SSH Linux targets, or
\l{Boot2Qt}{Boot2Qt devices}. \l{Boot2Qt}{Boot2Qt devices}.
\endlist \endlist
\endif
*/ */

View File

@@ -129,11 +129,11 @@
\section1 Providing Deployment Information \section1 Providing Deployment Information
If you want to run your application on a generic remote Linux device, If you want to run your application on a remote Linux device,
you first need to deploy your executable and possibly other files. you first need to deploy your executable and possibly other files.
\QC does that for you automatically if you provide the necessary \QC does that for you automatically if you provide the necessary
information. This works the same way as explained for CMake in information. This works the same way as explained for CMake in
\l {Deploying Applications to Generic Remote Linux Devices}, \l {Deploying to Remote Linux},
except that you also need to include your application binary in the list. except that you also need to include your application binary in the list.
\section1 Creating a Run Configuration \section1 Creating a Run Configuration

View File

@@ -30,7 +30,7 @@
\li \l{https://doc.qt.io/Boot2Qt/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 Remote Linux Devices}{Remote Linux Device}
\li \l{Connecting iOS Devices}{iOS Device} \li \l{Connecting iOS Devices}{iOS Device}
\li iOS Simulator \li iOS Simulator
\li \l{Connecting MCUs}{MCU Device} (commercial only) \li \l{Connecting MCUs}{MCU Device} (commercial only)

View File

@@ -9,11 +9,10 @@
// ********************************************************************** // **********************************************************************
/*! /*!
\previouspage creator-deployment-embedded-linux.html \previouspage creator-deployment-b2qt.html
\page creator-deployment-qnx.html \page creator-deployment-qnx.html
\nextpage creator-connecting-mobile.html \nextpage creator-deployment-embedded-linux.html
\title Deploying to QNX Neutrino
\title Deploying Applications to QNX Neutrino Devices
You can specify settings for deploying applications to QNX Neutrino You can specify settings for deploying applications to QNX Neutrino
devices in the project configuration file and in \uicontrol Projects devices in the project configuration file and in \uicontrol Projects
@@ -22,7 +21,7 @@
\image qtcreator-qnx-deployment.png "Deploy to device" \image qtcreator-qnx-deployment.png "Deploy to device"
The deployment process is described in more detail in The deployment process is described in more detail in
\l{Deploying Applications to Generic Remote Linux Devices}. \l{Deploying to Remote Linux}.
\section1 Finding Configured Devices \section1 Finding Configured Devices

View File

@@ -5,7 +5,7 @@
/*! /*!
\previouspage creator-developing-mcu.html \previouspage creator-developing-mcu.html
\page creator-developing-qnx.html \page creator-developing-qnx.html
\nextpage creator-setup-webassembly.html \nextpage creator-developing-generic-linux.html
\title Connecting QNX Devices \title Connecting QNX Devices
@@ -19,7 +19,7 @@
\section1 Adding a QNX Neutrino Device in \QC \section1 Adding a QNX Neutrino Device in \QC
Adding a QNX Neutrino device is very similar to Adding a QNX Neutrino device is very similar to
\l{Connecting Generic Remote Linux Devices}, except that \l{Connecting Remote Linux Devices}, except that
you need to select \uicontrol {QNX Device} in the you need to select \uicontrol {QNX Device} in the
\uicontrol {Device Configuration} wizard. \uicontrol {Device Configuration} wizard.

View File

@@ -139,9 +139,10 @@
\li \l{Running on Multiple Platforms} \li \l{Running on Multiple Platforms}
\li \l{Deploying to Devices} \li \l{Deploying to Devices}
\list \list
\li \l{Deploying Applications to Android Devices} \li \l{Deploying to Android}
\li \l{Deploying Applications to Generic Remote Linux Devices} \li \l{Deploying to Boot2Qt}
\li \l{Deploying Applications to QNX Neutrino Devices} \li \l{Deploying to QNX Neutrino}
\li \l{Deploying to Remote Linux}
\endlist \endlist
\li \l{Connecting Devices} \li \l{Connecting Devices}
\list \list
@@ -149,10 +150,10 @@
\li \l{Connecting Bare Metal Devices} \li \l{Connecting Bare Metal Devices}
\li \l{Connecting Boot2Qt Devices} \li \l{Connecting Boot2Qt Devices}
\li \l{Adding Docker Devices} \li \l{Adding Docker Devices}
\li \l{Connecting Generic Remote Linux Devices}
\li \l{Connecting iOS Devices} \li \l{Connecting iOS Devices}
\li \l{Connecting MCUs} \li \l{Connecting MCUs}
\li \l{Connecting QNX Devices} \li \l{Connecting QNX Devices}
\li \l{Connecting Remote Linux Devices}
\li \l{Building Applications for the Web} \li \l{Building Applications for the Web}
\endlist \endlist
\li \l{Customizing the Build Process} \li \l{Customizing the Build Process}

View File

@@ -2,7 +2,7 @@
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only // SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
/*! /*!
\previouspage creator-developing-qnx.html \previouspage creator-developing-generic-linux.html
\page creator-setup-webassembly.html \page creator-setup-webassembly.html
\nextpage creator-build-process-customizing.html \nextpage creator-build-process-customizing.html