Removal of Symbian support

Qt Creator's support for Symbian was at its peak in version
2.4.x. Nobody really verified it in Qt Creator 2.5 or 2.6.
It is most likely rotten. Let's remove it!

Also, the Symbian support code was spread throughout the whole
Qt Creator code base. The plugin interfaces evolved in the
meantime and target platforms like Android or QNX have 99% of
their code in separate plugins.

In case anyone wants to revive Symbian support in Qt Creator,
please create a plugin for it.

Change-Id: I56a758a3e2fd5b8c64d9aeb8f63d8e916c4883be
Reviewed-by: Alessandro Portale <alessandro.portale@nokia.com>

README

@@ -17,7 +17,7 @@ Compiling Qt Creator
 Prerequisites:
    * Qt 4.7.4
    * On Windows:
-     -  ActiveState Active Perl (version 5.8.9 for Symbian development)
+     -  ActiveState Active Perl
      -  MinGW 4.4 or later, Visual Studio 2008 or later
      -  jom
      The Qt SDK provides you with most of the required software.

doc/examples/batterystatus/BatteryStatus.pro

@@ -6,30 +6,14 @@ DEPLOYMENTFOLDERS = folder_01
 # Additional import path used to resolve QML modules in Creator's code model
 QML_IMPORT_PATH =
 
-symbian:TARGET.UID3 = 0xE54A5459
-
-# Smart Installer package's UID
-# This UID is from the protected range and therefore the package will
-# fail to install if self-signed. By default qmake uses the unprotected
-# range value if unprotected UID is defined for the application and
-# 0x2002CCCF value if protected UID is given to the application
-#symbian:DEPLOYMENT.installer_header = 0x2002CCCF
-
-# Allow network access on Symbian
-symbian:TARGET.CAPABILITY += NetworkServices
-
 # If your application uses the Qt Mobility libraries, uncomment the following
 # lines and add the respective components to the MOBILITY variable.
 CONFIG += mobility
 MOBILITY += systeminfo
 
-# Add dependency to symbian components
-CONFIG += qtquickcomponents
-
 # The .cpp file which was generated for your project. Feel free to hack it.
 SOURCES += main.cpp
 
 # Please do not modify the following two lines. Required for deployment.
 include(qmlapplicationviewer/qmlapplicationviewer.pri)
 qtcAddDeployment()
-

doc/examples/transitions/Transitions.pro

@@ -6,26 +6,11 @@ DEPLOYMENTFOLDERS = folder_01
 # Additional import path used to resolve QML modules in Creator's code model
 QML_IMPORT_PATH =
 
-symbian:TARGET.UID3 = 0xE506784B
-
-# Smart Installer package's UID
-# This UID is from the protected range and therefore the package will
-# fail to install if self-signed. By default qmake uses the unprotected
-# range value if unprotected UID is defined for the application and
-# 0x2002CCCF value if protected UID is given to the application
-#symbian:DEPLOYMENT.installer_header = 0x2002CCCF
-
-# Allow network access on Symbian
-symbian:TARGET.CAPABILITY += NetworkServices
-
 # If your application uses the Qt Mobility libraries, uncomment the following
 # lines and add the respective components to the MOBILITY variable.
 # CONFIG += mobility
 # MOBILITY +=
 
-# Add dependency to symbian components
-# CONFIG += qtquickcomponents
-
 # The .cpp file which was generated for your project. Feel free to hack it.
 SOURCES += main.cpp
 

doc/src/debugger/creator-debugger-setup.qdoc

@@ -135,10 +135,6 @@
             \o  Windows/MSVC
             \o  Microsoft Visual C++ Compiler
             \o  Debugging Tools for Windows/CDB
-        \row
-            \o  Symbian
-            \o  GCC
-            \o  GDB
         \row
             \o  Maemo, MeeGo
             \o  GCC
@@ -174,11 +170,6 @@
 
         \o  RemoteGdbAdapter interacts with the GDB server running on Linux.
 
-        \o  CodaGdbAdapter interacts with Symbian devices. The GDB protocol and
-            the GDB serial protocol are used between GDB and the adapter. The
-            target communication framework (TCF) protocol is used between the
-            adapter and the CODA debugging agent running on the device.
-
     \endlist
 
     \endomit

doc/src/debugger/creator-debugger.qdoc

@@ -242,7 +242,7 @@
     remote machine and a counterpart running on the host side.
     The probe is either integrated into the running process (e.g. for QML
     debugging) or runs a separate process (e.g. when using GDB server
-    on embedded Linux, or TRK/CODA on Symbian). The host side typically
+    on embedded Linux). The host side typically
     consists of \QC itself, often with the help of an external process, such as
     \if defined(qcmanual)
     GDB or CDB.
@@ -846,10 +846,6 @@
         \o  There is no Python-enabled GDB for Mac OS. Mac OS continues
             injection with C++ based debugging helpers.
 
-        \o  On the Symbian platform, an on-device debugging agent restricts the
-            communication between GDB and the device. Therefore, extracting
-            QObject properties, for example, is not possible.
-
         \o  There is no GDB to communicate with MSVC compiled applications on
             Windows. So information can be displayed nicely only in a limited
             fashion by using a cdb extension DLL.
@@ -1052,10 +1048,7 @@
 
         \o  \gui{putCallItem(self, name, value, func, *args)} -
             Uses GDB to call the function \c func on the value specified by
-            \a {value} and output the resulting item. This function is
-            not available when debugging core dumps and it is not available
-            on the Symbian platform due to restrictions imposed by the on-device
-            debugging agent.
+            \a {value} and output the resulting item.
 
         \o  \gui{putItem(self, value)} - The "master function", handling
             basic types, references, pointers and enums directly, iterates

doc/src/debugger/qtquick-debugging.qdoc

@@ -36,8 +36,7 @@
     Qt 4.8, or later.
 
     To debug Qt Quick applications running on devices, you must install
-    Qt 4.7.4, or later, libraries on devices. To debug applications on Symbian
-    devices, you must install also QML Viewer on them.
+    Qt 4.7.4, or later, libraries on devices.
 
     For an example of how to debug Qt Quick Projects, see
     \l{Debugging a Qt Quick Example Application}.

doc/src/howto/qtcreator-faq.qdoc

@@ -231,10 +231,6 @@
     \l{http://technet.microsoft.com/en-us/sysinternals/bb896647}{DebugView for Windows}
     to display output from GUI applications.
 
-    \if defined(qcmanual)
-    \input symbian/creator-faq-debug-output-symbian.qdocinc
-    \endif
-
     \section1 Questions about New Features
 
     \bold {Will a requested feature be implemented?}

doc/src/linux-mobile/creator-deployment-madde.qdoc

@@ -25,7 +25,7 @@
 
 /*!
     \contentspage index.html
-    \previouspage creator-deployment-symbian.html
+    \previouspage creator-deployment.html
     \page creator-deployment-maemo.html
     \nextpage creator-deployment-qnx.html
 

doc/src/linux-mobile/creator-publish-ovi-maemo.qdoc

@@ -25,7 +25,7 @@
 
 /*!
     \contentspage index.html
-    \previouspage creator-publish-ovi-symbian.html
+    \previouspage creator-publish-ovi.html
     \page creator-publish-ovi-maemo.html
     \nextpage creator-publish-ovi-meego.html
 

doc/src/linux-mobile/maemodev.qdoc

@@ -26,11 +26,7 @@
     \previouspage creator-developing-meego.html
     \endif
     \page creator-developing-maemo.html
-    \if defined(qcmanual)
-    \nextpage creator-developing-symbian.html
-    \else
-    \nextpage smartinstaller.html
-    \endif
+    \nextpage creator-developing-qnx.html
 
     \title Connecting Maemo Devices
 

doc/src/linux-mobile/meegodev.qdoc

@@ -20,11 +20,7 @@
     /*!
 
     \contentspage index.html
-    \if defined(qcmanual)
     \previouspage creator-connecting-mobile.html
-    \else
-    \previouspage creator-developing-symbian.html
-    \endif
     \page creator-developing-meego.html
     \if defined(qcmanual)
     \nextpage creator-developing-generic-linux.html

doc/src/overview/creator-deployment-overview.qdoc

@@ -27,7 +27,7 @@
     \contentspage index.html
     \previouspage creator-running-targets.html
     \page creator-deployment.html
-    \nextpage creator-deployment-symbian.html
+    \nextpage creator-deployment-maemo.html
 
     \title Deploying to Mobile Devices
 
@@ -38,13 +38,6 @@
 
     \list
 
-        \o  \l{Deploying Applications to Symbian Devices}
-
-            When you deploy the application for the \gui{Symbian Device} target,
-            \QC automatically generates a Symbian installation system (SIS) file
-            in the project folder and copies it to the connected device. You can
-            sign the SIS file and wrap it in a Nokia Smart Installer for Symbian
-            package. You can test and debug the application on the device.
         \o  \l{Deploying Applications to Linux-Based Devices}
 
             When you deploy the application on a Linux-based device target, such

doc/src/overview/creator-deployment-ovi.qdoc

@@ -27,7 +27,7 @@
     \contentspage index.html
     \previouspage creator-running-valgrind-remotely.html
     \page creator-publish-ovi.html
-    \nextpage creator-publish-ovi-symbian.html
+    \nextpage creator-publish-ovi-maemo.html
 
     \title Publishing
 
@@ -45,13 +45,6 @@
 
     \list
 
-        \o  \l{Publishing Qt Content for Symbian Devices}
-
-            The \gui {Publish Qt Symbian Applications to Nokia Store}
-            wizard ensures that your application can be published to Nokia
-            Store by verifying that the the application UID, vendor name,
-            and the capabilities used meet the Nokia Publish criteria.
-
         \o  \l{Publishing Qt Content for MeeGo Harmattan Devices}
 
             \QC generates installation packages that you can publish to