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

Blackberry: Remove blackberry support

Browse Source 
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: Tobias Hunger <tobias.hunger@theqtcompany.com>
This commit is contained in:
Tobias Hunger
2015-04-24 10:31:27 +02:00
parent b5090ddde4
commit 5b77a3a8c1
275 changed files with 504 additions and 27665 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/overview/creator-deployment-overview.qdoc
View File

@@ -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

12
doc/src/overview/creator-mobile-targets.qdoc
View File

@@ -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}

9
doc/src/overview/creator-target-platforms.qdocinc
View File

@@ -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.