Skip to content

GitLab

F
flatpak-qt-creator
Commit a9e4d6bf authored by Leena Miettinen's avatar Leena Miettinen
Browse files
Options

Doc: remove information about Necessitas SDK 

Support for Necessitas is removed from master.

Change-Id: I06682c2673e933777a14f016aed2e7dcfd2fea67
Reviewed-by: default avatarEskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
parent 72ac098a
Hide whitespace changes
Inline Side-by-side
Showing with 16 additions and 140 deletions
doc/src/android/androiddev.qdoc
View file @ a9e4d6bf
......@@ -53,13 +53,11 @@
\li \l{http://ant.apache.org/bindownload.cgi}{Apache Ant} 1.8.0, or
later
\li A tool chain for building applications for Android devices. You have
several options, such as the
\li A tool chain for building applications for Android devices provided
by the
\l{http://developer.android.com/sdk/index.html}{Android SDK} and
\l{http://developer.android.com/tools/sdk/ndk/index.html}
{Android NDK} from Google (supported for development with Qt 5) or the
\l{http://necessitas.kde.org/necessitas/necessitas_sdk_installer.php}
{Necessitas SDK} (supported for development with Qt 4).
{Android NDK} from Google.
\li On Windows, you also need the following:
......@@ -92,7 +90,7 @@
./android update sdk
\endcode
\section1 Developing with Qt 5
\section1 Setting Up the Development Environment
You must download and install the latest Android NDK and SDK, and update the
SDK to get the API and tools packages needed for development. In addition,
......@@ -142,50 +140,6 @@
\gui {Select Android Devices} dialog.
\endlist
\section1 Developing with Qt 4
The Necessitas SDK automatically sets the paths to the required software
in \QC, but you need to add the Qt version. \QC can then create the
necessary kits for you.
To configure connections between \QC and Android devices:
\list 1
\li Select \gui Tools > \gui Options > \gui {Build & Run} >
\gui {Qt Versions} > \gui Add to add the path to \c qmake path in
the Qt for Android SDK.
\li Select \gui Tools > \gui Options > \gui Android to check the paths
to the required software.
\image qtcreator-options-android.png "Android options"
\li Select the \gui {Automatically create kits for Android tool chains}
check box to allow \QC to create the kits for you. \QC displays a
warning if it cannot find a suitable Qt version.
\li To create an application, select \gui File >
\gui {New File or Project} > \gui Applications >
\gui {Qt Quick Application} > \gui Choose, and
follow the instructions of the wizard. For more information, see
\l{Creating Qt Quick Projects}.
\li To specify information for the Android manifest file, select
\gui Projects > \gui Run for the \gui Android kit.
\li Select \gui Details to view the
\gui {Package configurations}. For more information about the
options you have, see
\l{Specifying Settings for Qt 4 Packages}.
\li To specify settings for deploying applications to Android, select
\gui Details to view the \gui {Deploy configurations}. For more
information about the options you have, see
\l{Deploying Applications to Android Devices}.
\endlist
\section1 Selecting Android Devices
When you deploy an application to an Android device with Android
......@@ -231,10 +185,6 @@
\section1 Debugging on Android Devices
\QC is integrated with the GDB and GDB server that are delivered with the
Necessitas SDK. It provides GDB with Python support that enables \QC to
display custom Qt types, such as QString, QObject, and so on.
Android devices support debugging multi-thread applications in version
2.2.1 and later. If you use AVD, select Android 2.3, or later. For more
information, see the Android documentation.
......
doc/src/android/creator-projects-settings-run-android.qdocinc deleted 100644 → 0
View file @ 72ac098a
To configure Android packages, select \gui Projects >
\gui Run > \gui {Package configurations} > \gui Details. The Android system
uses the information from the file to start application components.
\image qtcreator-android-manifest.png "Package configuration"
\section2 Selecting API Level
In the \gui {Android target SDK} field, you can select the API level to use
for building the application. Usually, you should select the newest API
level available.
This field does not specify the minimum supported API level nor the target
API level, which you can specify in the Android manifest file.
For more information about Android API levels, see
\l{http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels}
{What is API Level?}.
\section2 Selecting Qt Libraries
In the \gui Libraries group, specify which Qt libraries the application uses.
To automatically determine this, select \gui {Read Information from
Application (Must Be Compiled)}. Alternatively, you can manually select the
Qt libraries and the external libraries you think your application needs.
Make sure to arrange the libraries so that depended libraries appear before
the ones that depend on them.
These entries are used by the Ministro tool to determine which Qt libraries
to download.
In addition, the Java Loader uses this list to determine which Qt Libraries
and other prebundled libraries to load with your application.
\section2 Signing Android Packages
In the \gui {Sign Package} group you can sign the Android package by using
a private key from the keystore. To create new keys, select \gui Create.
\image qtcreator-android-sign-package.png "Sign Package"
doc/src/android/deploying-android.qdoc
View file @ a9e4d6bf
......@@ -45,18 +45,13 @@
\endlist
The default option depends on whether you are developing with Qt 4 or Qt 5.
The Necessitas SDK does not support bundling Qt libraries with applications,
so you must use Ministro when developing with Qt 4. To specify the
deployment method, select \gui Projects > \gui Run >
\gui {Deploy configurations} > \gui Details
To specify the deployment method, select \gui Projects > \gui Run >
\gui {Deploy configurations} > \gui Details.
\section1 Creating Distributable APK Packages
To copy Qt libraries and files to the project directory and to bundle them
as part of the APK, select the \gui {Bundle Qt libraries in APK} option.
This is the default option when developing with Qt 5. It is not supported
when developing with Qt 4.
\section1 Using Ministro to Install Qt Libraries
......@@ -75,8 +70,6 @@
To use Ministro to install the Qt libraries, select the
\gui {Use Ministro service to install Qt} option.
This is the default option when developing with Qt 4.
\section1 Deploying Qt Libraries for Debugging
To test your application on a device that is physically connected to the
......@@ -97,13 +90,13 @@
\gui {Clean Temporary Libraries Directory on Device}. The next time you
deploy the application, Qt libraries are copied to the device again.
\section1 Packaging Qt 4 Applications
When you select a \gui {Qt for Android Kit} that specifies Qt 4 for a
project, \QC creates and maintains a set of files that are required to make
your application run on Android devices.
\section1 Packaging Applications
\QC adds the following files to your project:
Because bundling applications as APK packages is not
trivial, Qt 5 provides a deployment tool called \c androiddeployqt.
When you deploy an application using a \gui {Qt for Android Kit}, \QC uses
the \c androiddeployqt tool to create the necessary files and to bundle them
into an APK:
\list
......@@ -123,28 +116,6 @@
\endlist
\QC adds the files to the project to a subdirectory called \c android. The
contents of the \c android folder are used to create a distributable
application package.
To view the packages that \QC created, select the
\gui {Open package location after is complete} check box.
To specify information for the Android manifest file, open it in \QC. For
more information, see \l{Editing Manifest Files}.
\section2 Specifying Settings for Qt 4 Packages
\include creator-projects-settings-run-android.qdocinc
\section1 Packaging Qt 5 Applications
Because bundling applications as APK packages is not
trivial, Qt 5 provides a deployment tool called \c androiddeployqt.
When you deploy an application using a \gui {Qt for Android Kit}, \QC uses
the \c androiddeployqt tool to create the necessary files and to bundle them
into an APK.
To view the packages that the \c androiddeployqt tool created, select the
\gui {Open package location after build} check box.
......@@ -156,7 +127,7 @@
For more information about the \c androiddeployqt tool, see
\l{Deploying an Application on Android}.
\section2 Specifying Settings for Qt 5 Packages
\section2 Specifying Settings for Packages
You can specify settings for the \c androiddeployqt tool in \QC and in the
project .pro file. To specify settings in \QC, select
......@@ -220,10 +191,7 @@
\section1 Editing Manifest Files
When you develop with Qt 4, \QC creates the Android manifest file for you,
and you can open it for editing in the Android Manifest Editor.
When you develop with Qt 5, you can use the qmake variables to specify all
You can use the qmake variables to specify all
the settings you need for the \c androiddeployqt tool and you do not need an
Android manifest file until you want to publish the package in an
application store. To specify additional settings for APK packages, you can
......@@ -248,13 +216,10 @@
field, specify the version number that is shown to users.
In the \gui {Minimum required SDK} field, select the minimum API level
required to run the application. The minimum API level is android-4 for
Necessitas and android-9 for Qt 5. \QC does not allow you to select an API
required to run the application. The minimum supported API level is
android-9. \QC does not allow you to select an API
level that the Qt version specified for the kit does not support.
\note The android-4 API level does not support multitouch. If your
application needs multitouch, select a higher API level.
In the \gui {Target SDK} field, select the targeted API level of the
application. This affects the activation of some compatibility features in
the OS. The value used by the \c androiddeployqt tool by default is 14, which
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment