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

Doc: use \uicontrol command instead of \gui macro

Browse Source 
Change-Id: Idc898b6ac70b6d3186d353086b5f3e45830d1f83
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
This commit is contained in:
Leena Miettinen
2014-12-11 15:43:19 +01:00
committed by Leena Miettinen
parent c9696aa6f4
commit e1fbeedcd4
97 changed files with 1955 additions and 1876 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
doc/src/linux-mobile/creator-deployment-embedded-linux.qdoc
View File

@@ -33,14 +33,14 @@
You can specify settings for deploying applications to generic Linux devices
in the project .pro file.
You can view the settings in the
\gui {Run Settings}.
\uicontrol {Run Settings}.
\image qtcreator-embedded-linux-deployment-overview.png "Deploy to device"
The files to be installed are listed in the \gui {Deployment} step,
the \gui {Files to deploy} field. The \gui {Local File Path}
The files to be installed are listed in the \uicontrol {Deployment} step,
the \uicontrol {Files to deploy} field. The \uicontrol {Local File Path}
field displays the location of the file on the development PC. The
\gui {Remote Directory} field displays the folder where the file is
\uicontrol {Remote Directory} field displays the folder where the file is
installed on the device. Text in red color indicates that the information is
missing. Edit the qmake \l{Variables#installs}
{INSTALLS variable} in the project .pro file to add the missing files.
@@ -63,15 +63,15 @@
\image qtcreator-embedded-linux-deployment-details.png "Deploy to embedded Linux"
When you run the application on the \gui {Embedded Linux} device,
When you run the application on the \uicontrol {Embedded Linux} device,
\QC deploys the application as specified by the deploy steps. By default,
\QC copies the application files to the device by using the SSH file
transfer protocol (SFTP), as specified by the \gui {Upload files via SFTP}
transfer protocol (SFTP), as specified by the \uicontrol {Upload files via SFTP}
step.
If you have a lot of data to copy, select \gui Details in the
\gui {Upload Files via SFTP} step, and then select the
\gui {Incremental deployment} check box. \QC takes note of the deployment
If you have a lot of data to copy, select \uicontrol Details in the
\uicontrol {Upload Files via SFTP} step, and then select the
\uicontrol {Incremental deployment} check box. \QC takes note of the deployment
time and only copies files that have changed since the last deployment.
However, when you make major changes on the device, such as removing files
from the device manually or flashing a new disk image, or when you use
@@ -79,12 +79,12 @@
have \QC deploy all files again.
To only create a tarball and not copy the files to the device, select
\gui {Add Deploy Step > Create tarball}. Then remove all other deploy steps.
\uicontrol {Add Deploy Step > Create tarball}. Then remove all other deploy steps.
The \gui {Deploy tarball via SFTP upload} step specifies that \QC
The \uicontrol {Deploy tarball via SFTP upload} step specifies that \QC
uploads the tarball to the device and extracts it.
The \gui {Check for free disk space} step is by default the first deploy step.
The \uicontrol {Check for free disk space} step is by default the first deploy step.
Use it to find out whether the remote file system has enough space left to deploy your project.
Errors due to lack of disk space can otherwise be hard to detect.