Commit 5b77a3a8 authored by Tobias Hunger's avatar Tobias Hunger

Blackberry: Remove blackberry support

Keep QNX.

A short informal search did not turn up any more blackberry users,
even though there is interest in QNX. So this patch removes the
platform: We had no contact with the maintainers in months, there
are no changes going into the code for about as long.

I am not even aware of anybody testing the platform, so any
remaining users are probably better of with Qt Creator 3.2 or so
where the code was extensively tested.

Change-Id: Ibeda6bfd8565599918cfcc08fd01cb5ed8793dc2
Reviewed-by: default avatarTobias Hunger <tobias.hunger@theqtcompany.com>
parent b5090ddd
......@@ -21,7 +21,7 @@
\contentspage {Qt Creator Manual}
\previouspage creator-deployment.html
\page creator-deploying-android.html
\nextpage creator-deployment-bb10.html
\nextpage creator-deployment-embedded-linux.html
\title Deploying Applications to Android Devices
......
......@@ -21,7 +21,7 @@
\contentspage {Qt Creator Manual}
\previouspage creator-developing-android.html
\page creator-developing-baremetal.html
\nextpage creator-developing-bb10.html
\nextpage creator-developing-generic-linux.html
\title Connecting Bare Metal Devices
......
......@@ -371,10 +371,6 @@
\li \uicontrol Analyzer - Errors encountered while running the
\l{Analyzing Code}{Valgrind code analysis tools}.
\li \uicontrol {BAR Descriptor} - Errors and warnings encountered when using
the BlackBerry 10 BAR descriptor editor to customize the appearance
and behavior of an application.
\li \uicontrol {Build System} - Errors and warnings encountered during a
build.
......
......@@ -24,7 +24,7 @@
/*!
\contentspage {Qt Creator Manual}
\previouspage creator-deployment-bb10.html
\previouspage creator-deploying-android.html
\page creator-deployment-embedded-linux.html
\nextpage creator-deployment-qnx.html
......
......@@ -19,7 +19,7 @@
/*!
\contentspage {Qt Creator Manual}
\previouspage creator-developing-bb10.html
\previouspage creator-developing-baremetal.html
\page creator-developing-generic-linux.html
\nextpage creator-developing-ios.html
......
......@@ -42,11 +42,6 @@
When you deploy the application to an Android device, \QC copies
the application files to the device. In addition, you can determine
the Qt libraries to use.
\li \l{Deploying Applications to BlackBerry 10 Devices}
When you deploy the application to a BlackBerry 10 device, \QC generates a
BAR package in the build directory and deploys it to the connected
device.
\li \l{Deploying Applications to Embedded Linux Devices}
When you deploy the application to a generic Linux-based device, \QC
......@@ -54,9 +49,7 @@
can test and debug the application on the device.
\li \l{Deploying Applications to QNX Neutrino Devices}
When you deploy the application to a BlackBerry, \QC generates a
BAR package in the build directory and deploys it to the connected
device. When you deploy it 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 test and
debug the application on the device.
\endlist
......
......@@ -56,13 +56,6 @@
You can connect bare metal devices to the development PC and use \QC
to debug applications on them with GDB or a hardware debugger.
\li \l{Connecting BlackBerry 10 Devices}
\QC enables you to develop, deploy and debug your Qt applications
to BlackBerry 10.
You need to install the BlackBerry 10 NDK which contains a pre-built Qt.
You also need either a BlackBerry 10 device or the simulator.
\li \l{Connecting Embedded Linux Devices}
If you have a tool chain for building applications for embedded
......@@ -79,9 +72,8 @@
You can connect QNX devices to the development PC to deploy, run and
debug applications on them from within \QC. This is currently only
supported for BlackBerry Playbook and QNX Neutrino devices, and
requires the BlackBerry NDK or the QNX SDK to be installed on the
development PC.
supported for QNX Neutrino devices, and requires the QNX SDK to be
installed on the development PC.
\li \l{Connecting Windows Runtime Devices}
......
......@@ -8,8 +8,6 @@
\li Android
\li BlackBerry 10
\li Generic remote Linux
\li iOS
......@@ -37,11 +35,6 @@
\li \image ok
\li \image ok
\li \image ok
\row
\li BlackBerry 10
\li \image ok
\li \image ok
\li \image ok
\row
\li Generic Remote Linux
\li \image ok
......@@ -70,3 +63,5 @@
\note Madde support has been removed from \QC 3.0. To develop for Maemo or Harmattan,
use \QC 2.8.
\note BlackBerry 10 support has been removed from \QC 3.5. Use \QC 3.4 instead.
......@@ -65,8 +65,7 @@
to the directory where the compiler is located and select
the application binary interface (ABI) version from the list of available
versions. You can also create a custom ABI definition.
For QCC, also specify the path to the BlackBerry NDK or the QNX Software
Development Platform (SDP).
For QCC, also specify the path to the QNX Software Development Platform (SDP).
You specify the compiler to use for each kit in \uicontrol Tools >
\uicontrol Options > \uicontrol {Build & Run} > \uicontrol Kits.
......
......@@ -72,9 +72,8 @@
\image qt-creator-debugging-helpers.png
\li If the Qt version is for Blackberry or QNX, enter the path
to your installed Blackberry NDK or QNX SDK in the
\uicontrol {Blackberry Native SDK} or \uicontrol{QNX SDK} field respectively.
\li If the Qt version is for QNX, enter the path to your installed QNX SDK in the
\uicontrol{QNX SDK} field.
\endlist
......
......@@ -46,8 +46,6 @@
\li Bare Metal Device
\li BlackBerry 10 Device
\li Generic Linux Device
\li iOS Device
......
/****************************************************************************
**
** This file is part of Qt Creator
**
** Copyright (C) 2011 - 2014 Research In Motion
**
** Contact: Research In Motion (blackberry-qt@qnx.com)
** Contact: KDAB (info@kdab.com)
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\contentspage {Qt Creator Manual}
\previouspage creator-deploying-android.html
\page creator-deployment-bb10.html
\nextpage creator-deployment-embedded-linux.html
\title Deploying Applications to BlackBerry 10 Devices
To deploy Qt applications to BlackBerry 10 devices:
\list 1
\li Select \uicontrol File > \uicontrol {New File or Project}
> \uicontrol {Application} to create a
\uicontrol {Qt Quick Application}, \uicontrol {Qt Widgets
Application}, or \uicontrol {BlackBerry Cascades Application}.
\li Select a BlackBerry 10 \l{glossary-buildandrun-kit}{kit} for either device or simulator. For more information about adding kits, see \l{Connecting BlackBerry 10 Devices}.
\li When \QC prompts you to generate a BAR descriptor file, answer
\uicontrol Yes to generate the file and enable the packaging
process.
\li You can use the BAR descriptor editor to customize the appearance and behavior of the application.
\li You can specify which Qt libraries your application should link to
in the \uicontrol {Create Packages} deployment step,
\uicontrol {Package in development mode} option, if you create a
package in development mode:
\list
\li Select \uicontrol {Use Pre-installed Qt} to use Qt libraries
shipped with the device.
\li Select \uicontrol{Bundle Qt in Package} to package and use the
Qt version from the active BlackBerry kit.
This will significantly increase the size of your package.
\li To use a deployed Qt version in the device, select
\uicontrol{Use Deployed Qt} and set the path under
/accounts/devuser/ where Qt is deployed. To deploy a Qt version
select \uicontrol {Deploy Now}.
\image qtcreator-blackberry-deployQt.png "Use deployed Qt."
\endlist
\endlist
The BAR application descriptor file in your project will serve as a template to generate the actual BAR application descriptor file in the build directory
that is used for packaging. The final BAR application descriptor file
depends on the options you specify in the \uicontrol {Create Packages}
deployment step.
If you have an existing Cascades project created by QNX Momentics IDE, you can import it to \QC:
\list 1
\li Select \uicontrol File > \uicontrol {New File or Project} >
\uicontrol {Import Project} > \uicontrol {Momentics Cascades
Project} > \uicontrol Choose.
\li Specify an existing Cascades project created by QNX Momentics IDE.
\li Specify a location for the newly created \QC project.
\endlist
A project import report is generated into import.log file located in your project.
\note \uicontrol {BlackBerry Cascades Application} and \uicontrol {Momentics
Cascades Project} projects are available in the \uicontrol {All Templates}
filter, so you need to set this filter in the top-right corner of the
\uicontrol {New} dialog to enable those templates.
\note Currently, the BlackBerry 10 devices and Simulator have Qt 4.8 libraries preinstalled. To use Qt 5 features, you must compile the Qt libraries for BlackBerry 10 yourself. For more information, see \l {http://wiki.qt.io/Building_Qt5_for_Blackberry}{Building Qt5 for BlackBerry}.
For more details please refer to the Qt-Project wiki page: \l {http://wiki.qt.io/BlackBerry}{Qt for BlackBerry}.
*/
/****************************************************************************
**
** This file is part of Qt Creator
**
** Copyright (C) 2011 - 2014 Research In Motion
**
** Contact: Research In Motion (blackberry-qt@qnx.com)
** Contact: KDAB (info@kdab.com)
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
/*!
\contentspage {Qt Creator Manual}
\previouspage creator-developing-baremetal.html
\page creator-developing-bb10.html
\nextpage creator-developing-generic-linux.html
\title Connecting BlackBerry 10 Devices
\QC provides a plugin that enables you to develop for QNX and BlackBerry 10 platforms.
This page explains the basic steps to develop for BlackBerry 10 using \QC.
The native BlackBerry 10 NDK includes Qt 4 (4.8.4 or newer) for both simulator (x86) and device (arm) targets available for development. Compared with the development for the PlayBook, Qt libraries are integrated in the BlackBerry 10 device firmware and can be used by Qt applications as shared libraries.
Before starting to develop for BlackBerry 10 you need to download the following tools:
\list
\li \l {http://developer.blackberry.com/native/download/} {QNX Momentics IDE} - it is recommend to download the latest version to enable all \QC features
\li \l {http://developer.blackberry.com/native/download/} {BlackBerry 10 Simulator} if you do not have a BlackBerry 10 device
\li BlackBerry code signing keys (https://www.blackberry.com/SignedKeys/)
\endlist
\section1 Setting Up BlackBerry 10 Environment in Qt Creator
To check your BlackBerry 10 configuration, including the API level, the
Signing Keys and the Device registration, select \uicontrol Tools >
\uicontrol Options > \uicontrol BlackBerry > \uicontrol Setup.
\image qtcreator-blackberry-setupage.png "BlackBerry setup page"
\list 1
\li Set up API Levels:
\list 1
\li Select \uicontrol Tools > \uicontrol Options > \uicontrol BlackBerry >
\uicontrol {API Levels and Runtimes} to list all registered API Levels automatically
detected by \QC.
\image qtcreator-blackberry-apilevels.png "BlackBerry API leves and Runtimes page"
\li The API Levels printed with a bold font are active. Use
\uicontrol Activate and \uicontrol Deactivate to change it. When
an API Level is active, \QC registers kits, Qt versions, tool
chains, and debuggers to enable BlackBerry 10 development
against the API Level.
\li Use \uicontrol Add to install a new API Level or to register an
existing one.
\li It is recommended to keep the newest version as the default API level. \QC will use the available BlackBerry tools from the default API level to implement several of the plugin functions including device management, deployment process and the BlackBerry Signing Keys support. Some of those functions require 10.2 version or newer.
\endlist
\li Set up your Signing Keys:
\list 1
\li Select \uicontrol Tools > \uicontrol Options >
\uicontrol BlackBerry > \uicontrol Keys.
\li Register a BlackBerry Signing Authority - if you do not have any, the page will guide you to an online web form to request one.
\li Select \uicontrol {Create Certificate} to create a Developer
Certificate.
\li To package your application in development mode, select
\uicontrol Request to request a debug token or
\uicontrol Import to import a valid token.
\image qtcreator-blackberry-keys.png "BlackBerry Keys page"
You can also access the debug token list in \uicontrol Tools >
\uicontrol Options > \uicontrol Devices when you register a
BlackBerry device. To use the same debug token for different
devices, select \uicontrol{Edit} to add, remove or update the debug
token's device PINs.
\endlist
\li Register your device:
\list 1
\li On the device, select \uicontrol Settings >
\uicontrol {Security and Privacy} > \uicontrol {Development Mode}
to switch the BlackBerry 10 device to development mode.
\li Select \uicontrol Tools > \uicontrol Options > \uicontrol Devices
> \uicontrol Add > \uicontrol {Blackberry Device} to add a
BlackBerry Device. \QC should auto detect your BlackBerry device
if the default API level is set to 10.2 or newer.
\li In the \uicontrol {Device password} field, enter the device
password. \QC will query information from the device.
\image qtcreator-blackberry-add-device.png "BlackBerry Device Wizard"
\li Select \uicontrol Import to import a valid debug token for the
device or \uicontrol Request to request a new token.
\image qtcreator-blackberry-device-debugToken.png "BlackBerry Device debug token"
\li If your device is successfully added, it should be listed in
\uicontrol Tools > \uicontrol Options > \uicontrol {Devices}.
\image qtcreator-blackberry-device.png "BlackBerry Device Configuration page"
\li Select \uicontrol Upload to upload your debug token to the
device.
\li Select \uicontrol {Connect to device} to connect to the device.
You should close any other pending connections from a shell or
other IDE to successfully connect your device in \QC.
\li Select \uicontrol Tools > \uicontrol Options >
\uicontrol {Build & Run} > \uicontrol Kits to add your device to
compatible BlackBerry 10 kits.
\endlist
\endlist
\include qnx/creator-key-management-qnx.qdocinc
For more details please refer to the Qt-Project wiki page: \l {http://wiki.qt.io/BlackBerry}{Qt for BlackBerry}.
*/
......@@ -29,90 +29,6 @@
You can connect QNX devices to the development PC to deploy, run and debug
applications on them from within \QC.
\section1 Setting Up Connectivity on Playbook
In order to deploy applications to the Playbook, you will need to enable
Development Mode on the device and upload a debug token to it.
Enabling Development Mode is done by sliding top-down on the Playbook,
thereby opening the \uicontrol{Preferences}. Now go to \uicontrol{Security >
Development Mode} and set \uicontrol{Use Development Mode} to \uicontrol{ON}. Enter the
device password when asked to do so.
\image qtcreator-qnx-playbook-development-mode.png
\section2 USB Access
The \uicontrol{Development Address} shown in the \uicontrol{Development Mode} settings
is the IP address to use when you are connecting the device with a USB
cable to the development PC. If you are deploying over a Wi-Fi network, you
should use the IP address shown in \uicontrol{Preferences > About > Network}.
To enable access over USB, change \uicontrol{Preferences > Storage & Sharing >
USB Connections} to \uicontrol{Connect to Windows} if you are deploying from
Windows, or \uicontrol{Connect to Mac} if you are deploying from Linux or OS X.
\image qtcreator-qnx-playbook-storage-sharing.png
\section2 Debug Token
If you are using a physical device, you will have to upload a debug token to
the device. The simulator does not require any debug token.
\section3 Create a Debug Token
You can create the debug token either in QNX Momentics or from the command
line. There is currently no support for creating the debug token from
within \QC.
From the command line:
\c{blackberry-debugtokenrequest -storepass <pass> -devicepin <your PB pin> debugtoken.bar}
\section3 Install Debug Token on Playbook
You can install the debug token on the Playbook either in QNX Momentics or
from the command line. There is currently no support for installing the
debug token from within \QC.
From the command line:
\c{blackberry-nativepackage -installDebugToken ~/.rim/debugtoken.bar -device <device_ip> [-password <device_pass>]}
\section1 Adding a BlackBerry Device in \QC
Adding a BlackBerry device is done using a wizard in the \uicontrol{Device
Configurations} options. To launch it, go to \uicontrol Tools > \uicontrol Options >
\uicontrol Devices > \uicontrol Add > \uicontrol {BlackBerry Device} > \uicontrol {Start Wizard}.
\image qtcreator-qnx-device-configurations-wizard-1.png "Connection details"
\list
\li In the \uicontrol{The name to identify this configuration} field, enter a
name for the device.
\li In the \uicontrol{The device's host name or IP address} field, enter the
host name or IP address of the device.
\li In the \uicontrol{Device password} field, enter the password for the device.
\li In the \uicontrol{Device type} field, select whether it is a \uicontrol{Physical
device} or a \uicontrol{Simulator} you are connecting to.
\li In the \uicontrol{Debug token} field, enter the path to the debug token
that is also installed on the device. This is only necessary if you are
connecting to a \uicontrol{Physical device}.
\li Click \uicontrol{Next} to continue.
\endlist
\image qtcreator-qnx-device-configurations-wizard-2.png "SSH Key Setup"
For the \uicontrol{SSH Key Setup}, you can either select an existing \b{4096}-bit
key, or click \uicontrol{Generate} to create a new key. The generated key will be
stored next to the \QC settings, in a \b{qnx} sub-directory.
Click \uicontrol{Next} and then \uicontrol{Finish} to complete setting up the device
connection.
Once the device is added, you can edit the settings directly in \uicontrol Tools >
\uicontrol Options > \uicontrol Devices.
\image qtcreator-qnx-device-configurations.png "Devices"
\section1 Adding a QNX Neutrino Device in \QC
Adding a QNX Neutrino device is very similar to \l{Connecting Embedded
......
\section2 Obtaining New Keys
To request keys from the BlackBerry Signing Authority, select
\uicontrol Tools > \uicontrol Options > \uicontrol BlackBerry >
\uicontrol Keys > \uicontrol Register.
Then select the \uicontrol {BlackBerry website} link, and follow the
instructions.
\image qtcreator-blackberry-obtain-keys.png "Requesting new keys"
\section2 Registering Newly Obtained Keys
After you register in the BlackBerry website, you should get a bbidtoken.csk
file. Once you store it at the proper location as described in the email,
you can check that signing keys are registered in \QC by selecting
\uicontrol Tools > \uicontrol Options > \uicontrol BlackBerry >
\uicontrol Keys.
\image qtcreator-blackberry-registered-keys.png "Registered keys"
\section2 Creating a New Certificate
To create a new developer certificate, click the
\uicontrol {Create Certificate} button to open the
\uicontrol {Create Certificate} dialog.
\image qtcreator-blackberry-createcertificatedialog.png "Create Certificate dialog"
The fields you will need to fill in are:
\list
\li Author
The author, or owner of the certificate.
\li Password
The password which will be used to unlock the certificate from
they keystore.
\endlist
After filling in these fields, click \uicontrol OK and the certificate
will be created and registered in \QC.
\image qtcreator-blackberry-registered-certificate.png "Registered certificate"
......@@ -7,10 +7,7 @@
\li Configure the device and specify a connection to it. For more
information, see \l{Connecting QNX Devices}.
\li If you are running on a BlackBerry 10 device, create an Application
Descriptor File if it does not already exist. For more information, see \l{Deploying Applications to BlackBerry 10 Devices}.
\li Make sure that your kit has your QNX or BlackBerry 10 device set.
\li Make sure that your kit has your QNX device set.
\li Click the \uicontrol Run button.
......@@ -19,19 +16,13 @@
\QC uses the compiler specified in the QNX tool chain to build the
application.
If you are running on a BlackBerry device, \QC generates a BAR package,
installs it on the device, and executes the selected application. The
application views are displayed on the device. Standard output is
visible in the \QC \uicontrol {Application Output} view.
\note Debugging is currently only fully supported on Linux and OS X.
It is not possible to insert breakpoints during runtime on Windows.
\section2 Troubleshooting Errors
For the command-line output to show up in the \uicontrol{Application Output}
view when running on a BlackBerry device, \QC needs to be able to establish
an SSH connection to the device.
For the command-line output to show up in the \uicontrol{Application Output},
\QC needs to be able to establish an SSH connection to the device.
This is only possible if QNX Momentics is not running, and the SSH key
configured for the device is a 4096-bit key.
......
\section2 Specifying Run Settings for QNX Devices
To run and debug an application on a QNX or BlackBerry device, you must