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>
This commit is contained in:
Alessandro Portale
2012-08-22 13:27:25 +02:00
parent c107b10bae
commit ae23d50576
351 changed files with 150 additions and 27847 deletions

2
README
View File

@@ -17,7 +17,7 @@ Compiling Qt Creator
Prerequisites: Prerequisites:
* Qt 4.7.4 * Qt 4.7.4
* On Windows: * 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 - MinGW 4.4 or later, Visual Studio 2008 or later
- jom - jom
The Qt SDK provides you with most of the required software. The Qt SDK provides you with most of the required software.

View File

@@ -6,30 +6,14 @@ DEPLOYMENTFOLDERS = folder_01
# Additional import path used to resolve QML modules in Creator's code model # Additional import path used to resolve QML modules in Creator's code model
QML_IMPORT_PATH = 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 # If your application uses the Qt Mobility libraries, uncomment the following
# lines and add the respective components to the MOBILITY variable. # lines and add the respective components to the MOBILITY variable.
CONFIG += mobility CONFIG += mobility
MOBILITY += systeminfo MOBILITY += systeminfo
# Add dependency to symbian components
CONFIG += qtquickcomponents
# The .cpp file which was generated for your project. Feel free to hack it. # The .cpp file which was generated for your project. Feel free to hack it.
SOURCES += main.cpp SOURCES += main.cpp
# Please do not modify the following two lines. Required for deployment. # Please do not modify the following two lines. Required for deployment.
include(qmlapplicationviewer/qmlapplicationviewer.pri) include(qmlapplicationviewer/qmlapplicationviewer.pri)
qtcAddDeployment() qtcAddDeployment()

View File

@@ -1,80 +0,0 @@
/***************************************************************************
**
** Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies).
** All rights reserved.
** Contact: http://www.qt-project.org/
**
** This file is part of the documentation of Qt Creator.
**
** You may use this file under the terms of the BSD license as follows:
**
** "Redistribution and use in source and binary forms, with or without
** modification, are permitted provided that the following conditions are
** met:
** * Redistributions of source code must retain the above copyright
** notice, this list of conditions and the following disclaimer.
** * Redistributions in binary form must reproduce the above copyright
** notice, this list of conditions and the following disclaimer in
** the documentation and/or other materials provided with the
** distribution.
** * Neither the name of Nokia Corporation and its Subsidiary(-ies) nor
** the names of its contributors may be used to endorse or promote
** products derived from this software without specific prior written
** permission.
**
** THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
** "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
** LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
** A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
** OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
** SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
** LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
** DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
** THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
** (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
** OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."
**
****************************************************************************/
//! [3]
import QtQuick 1.1
import com.nokia.symbian 1.1
//! [3]
//! [4]
import QtMobility.systeminfo 1.2
//! [4]
//! [0]
Page {
id: mainPage
DeviceInfo {
id: deviceinfo
monitorBatteryLevelChanges: true
}
//! [0]
//! [1]
Text {
id: text1
x: 0
color: platformStyle.colorNormalLight
text: qsTr("Battery status: %1%").arg(progressbar1.value)
anchors.horizontalCenter: parent.horizontalCenter
anchors.verticalCenter: parent.verticalCenter
font.pixelSize: 20
}
//! [1]
//! [2]
ProgressBar {
id: progressbar1
anchors.horizontalCenter: text1.horizontalCenter
anchors.top: text1.bottom
anchors.topMargin: 20
minimumValue: 0
maximumValue: 100
value: deviceinfo.batteryLevel
}
//! [2]
}

View File

@@ -1,71 +0,0 @@
/***************************************************************************
**
** Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies).
** All rights reserved.
** Contact: http://www.qt-project.org/
**
** This file is part of the documentation of Qt Creator.
**
** You may use this file under the terms of the BSD license as follows:
**
** "Redistribution and use in source and binary forms, with or without
** modification, are permitted provided that the following conditions are
** met:
** * Redistributions of source code must retain the above copyright
** notice, this list of conditions and the following disclaimer.
** * Redistributions in binary form must reproduce the above copyright
** notice, this list of conditions and the following disclaimer in
** the documentation and/or other materials provided with the
** distribution.
** * Neither the name of Nokia Corporation and its Subsidiary(-ies) nor
** the names of its contributors may be used to endorse or promote
** products derived from this software without specific prior written
** permission.
**
** THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
** "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
** LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
** A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
** OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
** SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
** LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
** DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
** THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
** (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
** OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."
**
****************************************************************************/
import QtQuick 1.0
import com.nokia.symbian 1.0
Window {
id: window
StatusBar {
id: statusBar
anchors.top: window.top
}
PageStack {
id: pageStack
anchors { left: parent.left; right: parent.right; top: statusBar.bottom; bottom: toolBar.top }
}
ToolBar {
id: toolBar
anchors.bottom: window.bottom
tools: ToolBarLayout {
id: toolBarLayout
ToolButton {
flat: true
iconSource: "toolbar-back"
onClicked: pageStack.depth <= 1 ? Qt.quit() : pageStack.pop()
}
}
}
Component.onCompleted: {
pageStack.push(Qt.resolvedUrl("MainPage.qml"))
}
}

View File

@@ -6,26 +6,11 @@ DEPLOYMENTFOLDERS = folder_01
# Additional import path used to resolve QML modules in Creator's code model # Additional import path used to resolve QML modules in Creator's code model
QML_IMPORT_PATH = 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 # If your application uses the Qt Mobility libraries, uncomment the following
# lines and add the respective components to the MOBILITY variable. # lines and add the respective components to the MOBILITY variable.
# CONFIG += mobility # CONFIG += mobility
# MOBILITY += # MOBILITY +=
# Add dependency to symbian components
# CONFIG += qtquickcomponents
# The .cpp file which was generated for your project. Feel free to hack it. # The .cpp file which was generated for your project. Feel free to hack it.
SOURCES += main.cpp SOURCES += main.cpp

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.2 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

View File

@@ -135,10 +135,6 @@
\o Windows/MSVC \o Windows/MSVC
\o Microsoft Visual C++ Compiler \o Microsoft Visual C++ Compiler
\o Debugging Tools for Windows/CDB \o Debugging Tools for Windows/CDB
\row
\o Symbian
\o GCC
\o GDB
\row \row
\o Maemo, MeeGo \o Maemo, MeeGo
\o GCC \o GCC
@@ -174,11 +170,6 @@
\o RemoteGdbAdapter interacts with the GDB server running on Linux. \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 \endlist
\endomit \endomit

View File

@@ -242,7 +242,7 @@
remote machine and a counterpart running on the host side. remote machine and a counterpart running on the host side.
The probe is either integrated into the running process (e.g. for QML 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 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 consists of \QC itself, often with the help of an external process, such as
\if defined(qcmanual) \if defined(qcmanual)
GDB or CDB. GDB or CDB.
@@ -846,10 +846,6 @@
\o There is no Python-enabled GDB for Mac OS. Mac OS continues \o There is no Python-enabled GDB for Mac OS. Mac OS continues
injection with C++ based debugging helpers. 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 \o There is no GDB to communicate with MSVC compiled applications on
Windows. So information can be displayed nicely only in a limited Windows. So information can be displayed nicely only in a limited
fashion by using a cdb extension DLL. fashion by using a cdb extension DLL.
@@ -1052,10 +1048,7 @@
\o \gui{putCallItem(self, name, value, func, *args)} - \o \gui{putCallItem(self, name, value, func, *args)} -
Uses GDB to call the function \c func on the value specified by Uses GDB to call the function \c func on the value specified by
\a {value} and output the resulting item. This function is \a {value} and output the resulting item.
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.
\o \gui{putItem(self, value)} - The "master function", handling \o \gui{putItem(self, value)} - The "master function", handling
basic types, references, pointers and enums directly, iterates basic types, references, pointers and enums directly, iterates

View File

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

View File

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

View File

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

View File

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

View File

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

View File

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

View File

@@ -27,7 +27,7 @@
\contentspage index.html \contentspage index.html
\previouspage creator-running-targets.html \previouspage creator-running-targets.html
\page creator-deployment.html \page creator-deployment.html
\nextpage creator-deployment-symbian.html \nextpage creator-deployment-maemo.html
\title Deploying to Mobile Devices \title Deploying to Mobile Devices
@@ -38,13 +38,6 @@
\list \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} \o \l{Deploying Applications to Linux-Based Devices}
When you deploy the application on a Linux-based device target, such When you deploy the application on a Linux-based device target, such

View File

@@ -27,7 +27,7 @@
\contentspage index.html \contentspage index.html
\previouspage creator-running-valgrind-remotely.html \previouspage creator-running-valgrind-remotely.html
\page creator-publish-ovi.html \page creator-publish-ovi.html
\nextpage creator-publish-ovi-symbian.html \nextpage creator-publish-ovi-maemo.html
\title Publishing \title Publishing
@@ -45,13 +45,6 @@
\list \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} \o \l{Publishing Qt Content for MeeGo Harmattan Devices}
\QC generates installation packages that you can publish to \QC generates installation packages that you can publish to

View File

@@ -122,27 +122,6 @@
\list \list
\o Debugging large applications on Symbian devices using the Symbian^3
operating system might not work, because the on-device debugging
agent might not be able to access memory when the operating system
starts paging. This causes breakpoint handling and symbol resolution
to fail. For more information, see
\l{https://bugreports.qt-project.org/browse/QTCREATORBUG-2158}
{QTCREATORBUG-2158}.
As a workaround, add the following section to the application .pro
file to disable paging:
\code
debug {
MMP_RULES -= PAGED
MMP_RULES *= UNPAGED
}
\endcode
\note You must completely clean and rebuild the project for the
setting to take effect.
\o When debugging executables created by the GNU Compiler version 4.5.0 \o When debugging executables created by the GNU Compiler version 4.5.0
(all platforms), some data types will not be displayed in the (all platforms), some data types will not be displayed in the
\gui{Locals and Expressions} view due to missing debug information. \gui{Locals and Expressions} view due to missing debug information.

View File

@@ -65,15 +65,6 @@
Developer) to create the device-side end point for USB and WLAN Developer) to create the device-side end point for USB and WLAN
connections. connections.
\o \l{Connecting Symbian Devices}
You can run Qt applications on Symbian devices if the software
that Qt applications require (typically Qt, Qt Mobility, QtWebkit,
and Open C) is installed on the device. On Symbian Anna and later
devices, some version of Qt is pre-installed.
Install and launch the CODA on-device debugging agent on the
devices and connect the devices to the development PC.
\o \l{Connecting QNX Devices} \o \l{Connecting QNX Devices}
You can connect QNX devices to the development PC to deploy, run and You can connect QNX devices to the development PC to deploy, run and

View File

@@ -14,8 +14,6 @@
\o Generic remote Linux \o Generic remote Linux
\o Symbian
\o QNX \o QNX
\o Android \o Android
@@ -35,7 +33,6 @@
\o Maemo 5 \o Maemo 5
\o MeeGo Harmattan \o MeeGo Harmattan
\o Generic Remote Linux \o Generic Remote Linux
\o Symbian
\o QNX \o QNX
\o Android \o Android
@@ -46,7 +43,6 @@
\o Yes \o Yes
\o Yes \o Yes
\o Yes \o Yes
\o Yes
\o Yes (see \l{Running on QNX Devices} for limitations) \o Yes (see \l{Running on QNX Devices} for limitations)
\o Yes \o Yes
@@ -57,7 +53,6 @@
\o Yes \o Yes
\o Yes \o Yes
\o Yes \o Yes
\o Yes (by using Remote Compiler for building)
\o Yes \o Yes
\o Yes \o Yes
\row \row
@@ -67,7 +62,6 @@
\o Yes \o Yes
\o Yes \o Yes
\o Yes \o Yes
\o Yes (by using Remote Compiler for building)
\o Yes \o Yes
\o Yes \o Yes
\endtable \endtable

View File

@@ -55,9 +55,8 @@
\list 1 \list 1
\o Select at least \QS and one of the mobile \o Select at least \QS and one of the mobile
\l{glossary-development-target}{targets} (1), Symbian \l{glossary-development-target}{targets} (1), Maemo 5 or
Device, Maemo 5, or MeeGo Harmattan, depending on the device MeeGo Harmattan, depending on the device you develop for.
you develop for.
\o Select \gui {Configure Project} (2). \o Select \gui {Configure Project} (2).
@@ -87,17 +86,6 @@
can also simulate various mobile functions and create your own can also simulate various mobile functions and create your own
scripts. scripts.
\if defined(qcmanual)
\o To test the application on a Symbian device, check that the required
Qt libraries and a debugging agent are installed on the device. For
more information, see \l{Connecting Symbian Devices}.
\o Click the \gui {Target Selector} and select \gui {Symbian Device}.
\o Click \gui Run to build the application and run it on the Symbian
device.
\endif
\endlist \endlist
*/ */

View File

@@ -56,8 +56,4 @@
For more information on the options you have, see For more information on the options you have, see
\l{Specifying Build Settings}. \l{Specifying Build Settings}.
\if defined(qcmanual)
\input symbian/creator-projects-building-symbian.qdocinc
\endif
*/ */

View File

@@ -68,15 +68,6 @@
use \QC as a code editor and to fully control the steps and commands used to use \QC as a code editor and to fully control the steps and commands used to
build the project. build the project.
\if defined(qcmanual)
To develop applications for Symbian devices, you use qmake and the local
Symbian compiler (on Windows) or qmake and a compilation service at
Nokia Developer (on Linux and Mac OS) to build the applications for the
Symbian devices target. The interface to the compilation service,
Remote Compiler, is installed as a part of the \QSDK. For more information,
see \l{Building with Remote Compiler}.
\endif
You can install mobile device \l{glossary-development-target}{targets} You can install mobile device \l{glossary-development-target}{targets}
as part of the \QSDK. The build and run settings for the as part of the \QSDK. The build and run settings for the
installed targets are set up automatically. However, you might need to installed targets are set up automatically. However, you might need to
@@ -129,13 +120,6 @@
interfaces with a custom look and feel and QML and C++ code to interfaces with a custom look and feel and QML and C++ code to
implement the application logic implement the application logic
\o Qt Quick Application for Symbian
Use Qt Quick Components for Symbian to design a user interface
with the platform look and feel. Select this template to develop
for Symbian devices that support Qt 4.7.4 or later and have the
Qt Quick Components installed
\o Qt Quick Application for MeeGo Harmattan \o Qt Quick Application for MeeGo Harmattan
Use Qt Quick Components for MeeGo Harmattan to design a user Use Qt Quick Components for MeeGo Harmattan to design a user

View File

@@ -127,7 +127,6 @@
\code \code
win32:CONFIG(release, debug|release): LIBS += -L$$OUT_PWD/../../../projects/mylib/release/ -lmylib win32:CONFIG(release, debug|release): LIBS += -L$$OUT_PWD/../../../projects/mylib/release/ -lmylib
else:win32:CONFIG(debug, debug|release): LIBS += -L$$OUT_PWD/../../../projects/mylib/debug/ -lmylib else:win32:CONFIG(debug, debug|release): LIBS += -L$$OUT_PWD/../../../projects/mylib/debug/ -lmylib
else:symbian: LIBS += -lmylib
else:unix: LIBS += -L$$OUT_PWD/../../../projects/mylib/ -lmylib else:unix: LIBS += -L$$OUT_PWD/../../../projects/mylib/ -lmylib
INCLUDEPATH += $$PWD/../../../projects/mylib INCLUDEPATH += $$PWD/../../../projects/mylib
@@ -135,7 +134,7 @@
win32:CONFIG(release, debug|release): PRE_TARGETDEPS += $$OUT_PWD/../../../projects/mylib/release/mylib.lib win32:CONFIG(release, debug|release): PRE_TARGETDEPS += $$OUT_PWD/../../../projects/mylib/release/mylib.lib
else:win32:CONFIG(debug, debug|release): PRE_TARGETDEPS += $$OUT_PWD/../../../projects/mylib/debug/mylib.lib else:win32:CONFIG(debug, debug|release): PRE_TARGETDEPS += $$OUT_PWD/../../../projects/mylib/debug/mylib.lib
else:unix:!symbian: PRE_TARGETDEPS += $$OUT_PWD/../../../projects/mylib/libmylib.a else:unix: PRE_TARGETDEPS += $$OUT_PWD/../../../projects/mylib/libmylib.a
\endcode \endcode
\endlist \endlist

View File

@@ -73,7 +73,6 @@
\endlist \endlist
\if defined(qcmanual) \if defined(qcmanual)
\input symbian/creator-projects-qt-versions-symbian.qdocinc
\input qnx/creator-projects-qt-version-qnx.qdocinc \input qnx/creator-projects-qt-version-qnx.qdocinc
\endif \endif

View File

@@ -37,8 +37,7 @@
To run executable files without deploying them first, deselect the To run executable files without deploying them first, deselect the
\gui {Tools > Options > Project > Always deploy project before running it} \gui {Tools > Options > Project > Always deploy project before running it}
option. This allows you to test SIS files that you receive from Nokia option.
Publish or Symbian Signed after you have them signed, for example.
For more information on the options you have, see For more information on the options you have, see
\l{Specifying Run Settings}. \l{Specifying Run Settings}.
@@ -52,7 +51,6 @@
\if defined(qcmanual) \if defined(qcmanual)
\input linux-mobile/creator-projects-running-madde.qdocinc \input linux-mobile/creator-projects-running-madde.qdocinc
\input linux-mobile/creator-projects-running-generic-linux.qdocinc \input linux-mobile/creator-projects-running-generic-linux.qdocinc
\input symbian/creator-projects-running-symbian.qdocinc
\input qnx/creator-projects-running-qnx.qdocinc \input qnx/creator-projects-running-qnx.qdocinc
\endif \endif

View File

@@ -68,8 +68,6 @@
\o MeeGo Harmattan \o MeeGo Harmattan
\o Symbian Devices
\endlist \endlist
\section1 Starting External Processes \section1 Starting External Processes

View File

@@ -50,7 +50,6 @@
\input projects/creator-projects-settings-run-desktop.qdocinc \input projects/creator-projects-settings-run-desktop.qdocinc
\input projects/creator-projects-settings-run-analyze.qdocinc \input projects/creator-projects-settings-run-analyze.qdocinc
\input projects/creator-projects-settings-run-debug.qdocinc \input projects/creator-projects-settings-run-debug.qdocinc
\input symbian/creator-projects-settings-run-symbian.qdocinc
\input linux-mobile/creator-projects-settings-run-linux.qdocinc \input linux-mobile/creator-projects-settings-run-linux.qdocinc
\input qnx/creator-projects-settings-run-qnx.qdocinc \input qnx/creator-projects-settings-run-qnx.qdocinc
\input android/creator-projects-settings-run-android.qdocinc \input android/creator-projects-settings-run-android.qdocinc

View File

@@ -54,23 +54,10 @@
\o Clang is a C, C++, Objective C, and Objective C++ front-end for the \o Clang is a C, C++, Objective C, and Objective C++ front-end for the
LLVM compiler for Windows, Linux, and Mac OS X. LLVM compiler for Windows, Linux, and Mac OS X.
\o GCCE (GNU Compiler Collection for Embedded) is an ARM-based
compiler used in Symbian OS 9 and distributed together with \QSDK.
\if defined(qcmanual)
\o RVCT is an ARM-based compiler for building applications for Symbian
devices (requires a license).
\o WINSCW is a compiler for building applications that can be run or
debugged on the Symbian Emulator. It is distributed together with
Symbian SDKs (but not with the \QSDK).
\endif
\endlist \endlist
To build an application using GCC, MinGW, GCCE, or Clang, specify the paths To build an application using GCC, MinGW, or Clang, specify the paths
to the directories where the compiler is located and select to the directories where the compiler and debugger are located and select
the application binary interface (ABI) version from the list of available the application binary interface (ABI) version from the list of available
versions. You can also create a custom ABI definition. versions. You can also create a custom ABI definition.
@@ -100,12 +87,6 @@
The other settings to specify depend on the tool chain. The other settings to specify depend on the tool chain.
\if defined(qcmanual)
\o For RVCT, select the ARM version to use in the \gui {ARM version}
field. RVCT 2.2 is supported on Symbian Anna and earlier. RVCT 4.0 b902
or later is required for Symbian Belle.
\endif
\endlist \endlist
\section2 Troubleshooting MinGW Compilation Errors \section2 Troubleshooting MinGW Compilation Errors

View File

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

View File

@@ -107,7 +107,6 @@
\o \list \o \list
\o \bold {\l{Publishing}} \o \bold {\l{Publishing}}
\list \list
\o \l{Publishing Qt Content for Symbian Devices}
\o \l{Publishing Qt Content for MeeGo Harmattan Devices} \o \l{Publishing Qt Content for MeeGo Harmattan Devices}
\o \l{Publishing Qt Content for Maemo Devices} \o \l{Publishing Qt Content for Maemo Devices}
\o \l{Publishing Maemo Applications to Extras-devel} \o \l{Publishing Maemo Applications to Extras-devel}
@@ -237,7 +236,6 @@
\o \l{Running on Multiple Targets} \o \l{Running on Multiple Targets}
\o \l{Deploying to Mobile Devices} \o \l{Deploying to Mobile Devices}
\list \list
\o \l{Deploying Applications to Symbian Devices}
\o \l{Deploying Applications to Linux-Based Devices} \o \l{Deploying Applications to Linux-Based Devices}
\o \l{Deploying Applications to QNX Devices} \o \l{Deploying Applications to QNX Devices}
\o \l{Deploying Applications to Android Devices} \o \l{Deploying Applications to Android Devices}
@@ -247,7 +245,6 @@
\o \l{Connecting MeeGo Harmattan Devices} \o \l{Connecting MeeGo Harmattan Devices}
\o \l{Connecting Embedded Linux Devices} \o \l{Connecting Embedded Linux Devices}
\o \l{Connecting Maemo Devices} \o \l{Connecting Maemo Devices}
\o \l{Connecting Symbian Devices}
\o \l{Connecting QNX Devices} \o \l{Connecting QNX Devices}
\o \l{Connecting Android Devices} \o \l{Connecting Android Devices}
\endlist \endlist
@@ -282,7 +279,6 @@
\endlist \endlist
\o \l{Publishing} \o \l{Publishing}
\list \list
\o \l{Publishing Qt Content for Symbian Devices}
\o \l{Publishing Qt Content for Maemo Devices} \o \l{Publishing Qt Content for Maemo Devices}
\o \l{Publishing Qt Content for MeeGo Harmattan Devices} \o \l{Publishing Qt Content for MeeGo Harmattan Devices}
\o \l{Publishing Maemo Applications to Extras-devel} \o \l{Publishing Maemo Applications to Extras-devel}

View File

@@ -27,7 +27,6 @@
\contentspage index.html \contentspage index.html
\previouspage creator-tutorials.html \previouspage creator-tutorials.html
\page creator-qml-application.html \page creator-qml-application.html
\nextpage creator-qml-components-example.html
\title Creating a Qt Quick Application \title Creating a Qt Quick Application

View File

@@ -73,7 +73,7 @@
application wizards import Qt Quick 1.1, and therefore, you can use them application wizards import Qt Quick 1.1, and therefore, you can use them
without changes if you target only platforms that run Qt 4.7.4 (such as without changes if you target only platforms that run Qt 4.7.4 (such as
MeeGo or the desktop). If you also target platforms that run Qt 4.7.3 MeeGo or the desktop). If you also target platforms that run Qt 4.7.3
(such as Maemo and S60 5th Edition), you must change the import statement to (such as Maemo), you must change the import statement to
import Qt Quick 1.0. import Qt Quick 1.0.
\endif \endif
@@ -137,9 +137,7 @@
\note We recommend that you use the \gui {Qt Quick Application for \note We recommend that you use the \gui {Qt Quick Application for
MeeGo Harmattan} template when you develop for MeeGo Harmattan MeeGo Harmattan} template when you develop for MeeGo Harmattan
devices and the \gui {Qt Quick Application for Symbian} template devices.
when you develop for Symbian devices that support Qt 4.7.4, or
later.
The \gui{Introduction and Project Location} dialog opens. The \gui{Introduction and Project Location} dialog opens.
@@ -174,25 +172,11 @@
application behaves when the orientation of the device display application behaves when the orientation of the device display
rotates between portrait and landscape, and then click \gui Next. rotates between portrait and landscape, and then click \gui Next.
\note This dialog opens only if you select \gui Maemo5 or \note This dialog opens only if you select \gui Maemo5
\gui {Symbian Device} target in the \gui {Target Setup} dialog. On target in the \gui {Target Setup} dialog. On
Harmattan, the Qt Quick Components for MeeGo provide native-looking Harmattan, the Qt Quick Components for MeeGo provide native-looking
rotation. rotation.
The \gui {Symbian Specific} dialog opens.
\image qmldesigner-new-project-symbian-options.png "Symbian Specific dialog"
\o In the \gui {Application icon (.svg)} field, select an application
icon for the \gui {Symbian Device} target, or use the default icon.
\o In the \gui {Target UID3} field, specify the \l{Application UID}, or
use the default UID.
\note \QC generates a UID for testing the application on a device.
You need to change the UID when you deliver the application for
public use.
\o Click \gui Next. \o Click \gui Next.
The \gui {Harmattan Specific} dialog opens. The \gui {Harmattan Specific} dialog opens.
@@ -217,7 +201,7 @@
\endlist \endlist
\QC creates the necessary boilerplate files. Some of the files are \QC creates the necessary boilerplate files. Some of the files are
specific to the Symbian, Maemo, or MeeGo Harmattan platform. specific to the Maemo or MeeGo Harmattan platform.
\section1 Importing QML Applications \section1 Importing QML Applications

View File

@@ -151,11 +151,6 @@
\list \list
\if defined(qcmanual)
\o \c {import com.nokia.symbian 1.0} for Symbian (Qt 4.7)
\o \c {import com.nokia.symbian 1.1} for Symbian (Qt 4.8)
\endif
\o \c {import com.nokia.meego 1.0} for MeeGo \o \c {import com.nokia.meego 1.0} for MeeGo
\endlist \endlist

View File

@@ -1,370 +0,0 @@
/****************************************************************************
**
** This file is part of Qt Creator
**
** Copyright (c) 2012 Nokia Corporation and/or its subsidiary(-ies).
**
** Contact: http://www.qt-project.org/
**
**
** 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 index.html
\previouspage creator-deployment.html
\page creator-deployment-symbian.html
\nextpage creator-deployment-maemo.html
\title Deploying Applications to Symbian Devices
This section describes how to create installation packages that meet the
requirements for installing applications to Symbian devices.
\section1 Creating SIS Files
When you deploy the application for the \gui{Symbian Device} target, \QC
automatically generates a Symbian installation system (SIS) file
in the project folder. You can deliver the installation file to users for
installation on Symbian devices.
The name of the installation file is displayed in the \gui {Installation file}
field in the \gui {Run Settings}. In the \gui {Installation drive} field, select the drive on the device
to install the application to. To suppress notifications on the device during the
installation, select the \gui {Silent installation} check box. If the silent
installation fails, \QC attempts installation again, this time displaying
notifications and error messages.
To create a SIS package without copying it to the device (for example, to submit it
to \e {Application Signing Services for Nokia Store} or \e {Symbian Signed}),
create a deploy configuration that contains only the
\gui {Create SIS Package} step.
\image qtcreator-run-settings-create.png "Create SIS Package step"
\section1 Signing SIS Files
Only installation files signed with a certificate and private key are
allowed to be installed onto Symbian devices. By default, \QC
self-signs the installation file. This self-signing allows you to install
the application on a mobile device but places limits on what you can do
with the installation file, including:
\list
\o Self-signed applications cannot access the more sensitive
\l{Capabilities and Signing}{capabilities} of the mobile device.
\o Security warnings will be displayed when you install the self-signed
application on a mobile device.
\o Self-signed applications cannot be published to Nokia
Store.
\endlist
To get around these limitations, you need to go through the Symbian Signed
or Application Signing Services for Nokia Store. The Symbian Signed organisation
manages a public key
infrastructure to provide public authentication of the information in the
application signing certificates. Their security partner can validate your
certificate and give you a Publisher ID. Then, when you sign an
application, other people can be confident that the information in your
certificate is correct and that the application does actually come from you.
Application Signing Services for Nokia Store is a variant of the Symbian
Signed certification provided by Nokia
Publish. It is limited to the Basic and System capability sets
(Express Signing). Participants can submit an unsigned SIS file to Nokia
Publish for signing. For more information about how
to participate, see
\l {http://www.developer.nokia.com/Community/Wiki/Guide_to_Publishing_Qt_Applications_to_the_Ovi_Store}{Guide to Publishing Qt Applications to the Nokia Store}.
There are also options that do not require you to get a Publisher ID. For
more detail about how the Symbian Signed process works, see
\l{https://www.symbiansigned.com}{Symbian Signed}.
When you have your own certificate and private key, you can specify them in
the \gui{Create SIS Package} step in the \gui {Run Settings}.
\image qtcreator-qt4-symbian-signing.png
If your private key is protected by a passphrase, \QC asks you for the
passphrase when the package is signed and offers to store it. However, storing
passphrases in \QC presents a security risk. To make \QC forget
all saved passphrases, click \gui {Reset Passphrases}.
\section2 Capabilities and Signing
Capabilities allow the Symbian platform to control access by applications to
the functionality provided by the platform APIs. Access to capabilities is
determined by the device configuration and how the application has been signed.
Symbian Signed offers the following signing options depending on the
capabilities that the application accesses:
\list
\o \bold{Express signed} for applications that access only user and system
capabilities.
\o \bold{Certified signed} for applications that access also restricted or
device manufacturer capabilities.
\note You need to request the rights to access device manufacturer
capabilities from the manufacturer.
\endlist
For more information about how to choose the appropriate signing option and
how you can check which capabilities you need, see
\l{https://www.symbiansigned.com}{Symbian Signed}
and
\l{http://doc.qt.nokia.com/4.7/platform-notes-symbian.html#required-capabilities}{Required Capabilities for Qt Applications}.
For more information on how to define capabilities for a project, see
\l{http://doc.qt.nokia.com/4.7/qmake-platform-notes.html#capabilities}{Capabilities}.
\note In Qt 4.7.1 and later, if you select the \gui {Self-signed certificate}
option, the SIS generation process checks that the package can be self-signed.
If problems are found, it attempts to fix the package. If fixes cannot be made,
a message appears in the \gui {Compile Output} view.
The following modifications can be made:
\list
\o Package UID is changed to an UID from the unprotected range (if it was
from the protected range).
\o Vendor ID is set to zero on all binaries included in the package file.
\o All restricted and device manufacturer capabilities are removed from all
libraries included in the package file.
\endlist
The application UID or capabilities used in executables (.exe) cannot be changed,
because that would break the application. If the executables use protected UIDs
or restricted or device manufacturer capabilities, signing fails and an error
message appears in the \gui {Compile Output} view.
\section1 Creating Smart Installer for Symbian Packages
You can run Qt applications on Symbian devices if the software that Qt
applications require (typically Qt, Qt Mobility, QtWebkit, and Open C) is
installed on the device. On Symbian^3 and later devices, some version of Qt
is pre-installed. On earlier devices, you must install the modules that Qt
applications require. Nokia Smart Installer for Symbian makes it easier
for users to install Qt applications to Symbian phones by checking whether the device contains
the necessary software and by installing the missing pieces.
For this to work, the Nokia Smart Installer must be packaged with the Qt application. The
application SIS file must first be Symbian Signed or signed by the Application
Signing Services for Nokia Store. The capabilities used in the applications
determine, which signing option must be selected. The wrapper package must be signed using
either the same option or a more extensive option than the application SIS.
\note If you use the Application Signing Services for Nokia Store, you can submit an unsigned
wrapper package to Nokia Publish. For more information, see
\l{Publishing Qt Content for Symbian Devices}.
You can either install the Nokia Smart Installer for Symbian as part of
the \QSDK, or download and install it from the
\l{http://www.developer.nokia.com/Community/Wiki/Nokia_Smart_Installer_for_Symbian}{Nokia Smart Installer for Symbian}
wiki.
To package Nokia Smart Installer with the application, select the \gui {Create Smart Installer
package} check box. This ensures that up-to-date and appropriate versions of Qt and its
dependencies are installed on devices. Further, it reduces the file size of the application you
publish, because you do not have to deliver the required libraries.
Nokia has reserved the following UIDs to be used with Nokia Smart Installer for Symbian:
\list
\o 0xA000D7CE for self-signed applications
\o 0x2002CCCF for Nokia Store or Symbian Signed packages
\endlist
\section2 Creating Self-signed Smart Installer Packages
To create a self-signed Nokia Smart Installer for Symbian wrapped .sis file,
you must use an UID from the unprotected UID range, provided by Symbian Signed
and the wrapper package UID value 0xA000D7CE. If you used the \QC project
wizard to create the project, this wrapper package UID is used by default.
\list 1
\o Make sure that the source directory is clean. For example, if you use Git,
enter the following command:
\c {git clean -dfx}
\o Click \gui Projects to edit the \gui {Build Settings} for the
\gui {Symbian Device} target.
\o Select the \gui Release configuration.
\o Open the \gui {Run Settings}.
\o In the \gui {Create SIS Package} step, select \gui {Self-signed certificate}.
\o In the \gui {Deploy SIS Package} step, click \gui {Remove Item} (1) to
skip the step of copying the SIS file to a device. The SIS file is created
in the project folder.
\image qtcreator-remove-deploy-step.png "Removing deploy steps"
\o To package Nokia Smart Installer for Symbian with the application, select
the \gui {Create Smart Installer package} check box.
\o Edit the project .pro file to use the correct UIDs for the application and
the wrapper package, as illustrated by the following code snippet:
\code
symbian {
TARGET.UID3 = 0xE4DE5D27
DEPLOYMENT.installer_header=0xA000D7CE
vendorinfo = \
"%{\"CustomVendor-EN\"}" \
":\"CustomVendor\""
my_deployment.pkg_prerules = vendorinfo
DEPLOYMENT += my_deployment
}
\endcode
\o Choose \gui {Build > Run Project}.
\endlist
\QC automatically generates a wrapper package in the project folder.
\section2 Creating Symbian Signed Smart Installer Packages
If the application uses functions that require advanced capabilities (AllFiles,
DRM, TCB, CommDD, DiskAdmin, NetworkControl, MultimediaDD), you must use the
standard Symbian Signed process to have the application Symbian Signed. Depending
on the capabilities used, you may use either the Express Signed or the Certified
Signed path, or the manufacturer-specific channel (for AllFiles, DRM, and TCB).
\list 1
\o Make sure that the source directory is clean. For example, if you use Git,
enter the following command:
\c {git clean -dfx}
\o Click \gui Projects to edit the \gui {Build Settings} for the
\gui {Symbian Device} target.
\o Select the \gui Release configuration.
\o Open the \gui {Run Settings}.
\o In the \gui {Create SIS Package} step, specify the developer certificate
and key in the \gui {Custom certificate} and \gui {Key file} fields.
\o In the \gui {Deploy SIS Package} step, click \gui {Remove Item} to
skip the step of copying the SIS file to a device. The SIS file is created
in the project folder.
\o Edit the project .pro file to use the correct UIDs and vendor information
for the application, as illustrated by the following code snippet:
\code
symbian {
TARGET.UID3 = 0x2000D7D1
DEPLOYMENT.installer_header=0x2002CCCF
vendorinfo = \
"%{\"CustomVendor-EN\"}" \
":\"CustomVendor\""
my_deployment.pkg_prerules = vendorinfo
DEPLOYMENT += my_deployment
}
\endcode
\o Choose \gui {Build > Run Project}.
\o Submit the created .sis file to Symbian Signed for certification.
\note Ensure that your application complies with the Symbian Signed
Test Criteria before submitting the file for certification. Also, if the file is
intended for Nokia Store publishing, verify that the application complies with Nokia
Store publishing requirements.
\o After receiving the .sis file from Symbian Signed, copy it over the old
application.sis.
\note The instructions below assume that you have installed \QSDK.
\o To package Nokia Smart Installer for Symbian with the application, choose
\gui {Start > Qt SDK > Symbian > Qt for Symbian Command Prompt}
to open the Qt command line environment.
\o Change to the project directory. For example:
\c{cd C:\Sources\Application}
\o To create a Smart Installer wrapper package, enter the following
command:
\c {C:\Sources\Application> make ok_installer_sis QT_SIS_CERTIFICATE=publisherid.cer QT_SIS_KEY=publisherid.key}
\o Submit the created wrapped .sis file, application_installer.sis, to
Symbian Signed. Express Signed is a suitable signing option for the wrapper
package. The capabilities used in the application do not play a role here,
because the wrapper package is already signed.
\endlist
\QC automatically generates a wrapper package in the project folder.
\note Ensure that your application complies with the requirements before submitting
the file to Nokia Store.
For more information about the qmake DEPLOYMENT variable, see
\l{http://doc.qt.nokia.com/4.7/qmake-variable-reference.html#deployment}{qmake Variable Reference}.
For more information about the Nokia Smart Installer, see the
\l{http://doc.qt.nokia.com/smart-installer/index.html}{Nokia Smart Installer for Symbian Manual}.
Note: Nokia Smart Installer for Symbian is only available on Windows.
\section1 Application UID
A UID is a globally unique identifier that is used to
uniquely identify, for example, an object or file type. In Symbian development,
objects are identified by compound identifiers that are constructed from three
UIDs, namely UID1, UID2, and UID3. UID1 and UID2 specify the category of an
object, whereas UID3 identifies a particular object, such as an application.
When you create a \gui {Mobile Qt Application}, \QC adds a UID3 suitable for
development and debugging automatically to the application .pro file. However, to
distribute your application and get it Symbian Signed, you must apply for a UID
from Symbian Signed, which manages the allocation of UIDs. You can request UIDs either one
at a time or as preallocated blocks on the \l{https://www.symbiansigned.com/app/page}{Symbian Signed}
web site.
If you use the Nokia Signed process, Nokia Publisher Support allocates the UID for you.
Replace the testing UID with the distribution UID in the .pro file before you
build the final installation package. For more information, see
\l{http://doc.qt.nokia.com/4.7/qmake-platform-notes.html#unique-identifiers}{Unique Identifiers}.
*/

View File

@@ -1,13 +0,0 @@
\bold {On Symbian OS}: \c qDebug() and related functions use the native
\c RDebug::Print functionality.
When you use the Symbian emulator on Windows, the output is redirected to
standard debug output. To view it, you can use a Windows debug output
viewer, such as the DebugView for Windows.
On devices, the \c RDebug output is intercepted by \e CODA or \e {App TRK}
and then propagated to \QC, which displays it in the
\gui {Application Output} pane.
Symbian OS provides no support for differentiating between standard output
and error output.

View File

@@ -1,25 +0,0 @@
\section1 Building for Symbian
The tool chain for building applications locally on the development PC for
the \gui {Symbian Device} target is only supported on Windows.
If you develop on Linux or Mac OS, you must use the Remote Compiler
interface to a compilation service at Nokia Developer. For more information,
see \l{Building with Remote Compiler}.
\section2 Troubleshooting Build Issues
If you cannot build the application for a Symbian device, check that:
\list
\o You selected the Symbian Device target to build the application.
\o You selected the correct Qt version to build the application.
For more information, see \l{Selecting Qt for Symbian Versions}.
\endlist
\section1 Building for Symbian Emulator
\QC does not create release configurations for the \gui {Symbian Emulator}
target, because Symbian Emulator supports only debug builds.

View File

@@ -1,22 +0,0 @@
\section2 Setting Up Qt for Symbian Versions
If you install Qt for Symbian as a part of \QSDK, it is automatically
detected by \QC. If you install other Symbian SDKs and register them
with devices.exe, \QC automatically detects the Qt version.
The \gui {S60 SDK} field displays the path to the directory where
the Symbian SDK is located.
If the selected Qt version was built using the SBSv2 build system, that
is available for Symbian OS 9.5 based SDKs, \QC builds your projects
using this build system. The \gui {SBS v2 directory} field displays the
path to the directory where the SBS executable (for
example, sbs.bat on Windows) is located.
To view Qt for Symbian version settings, select \gui {Tools > Options >
Build & Run > Qt Versions}.
\image qtcreator-qt4-qtversions-win-symbian.png
For more information about how to add tool chains for using the GCCE and
WINSCW compilers, see \l{Adding Tool Chains}.

View File

@@ -1,96 +0,0 @@
\section1 Running on Symbian
\list 1
\o Build and run the application for \l{Running on Qt Simulator}
{\QS}.
\o If no problems are found, build and run the application for a
device.
\o To test functionality that uses Symbian APIs, you can build and
run the application for Symbian Emulator.
\endlist
\section2 Running on a Device
\list 1
\o Install the required software on the device. For more information,
see \l{Connecting Symbian Devices}.
\o Connect the device to the development PC through a USB cable.
The target selector displays a green check mark when a device is
connected.
\image qtcreator-qt4-symbian-device-connected.png
The tool tip of the target selector shows more details about the
actual device that will be used when you run your application.
\o Start the CODA debugging agent on the device.
\note If you use CODA over an USB connection, it starts up
automatically when you connect the device to the development PC.
\o Click the \gui Run button.
\endlist
You can connect several devices to your development PC simultaneously.
In the details of the run configuration for the \gui{Symbian Device} target,
select the device to run your application on.
When your application is ready for delivery to users, specify run settings
for creating the final SIS installation packages. For more information,
see \l{Creating SIS Files}.
If you cannot run the application on a device, check that:
\list
\o The Nokia USB drivers that come with \e{PC Suite} or \e{Ovi Suite}
have been installed on the development PC.
\o The device is connected through USB cable in \e{PC Suite} mode.
\o The CODA debugging agent is installed on the device and it is
running with the status \e connected.
\note If you use the CODA debugging agent over WLAN, you must enter
the WLAN address and port number in \QC, separated by a colon (:).
For example: 192.167.0.100:1534
\o The device is detected and selected in the \gui {Run Settings}.
\endlist
If this does not help to solve your problem, search the
qt-creator@trolltech.com mailing list archives or provide feedback to us via
the methods described on the
\l{http://developer.qt.nokia.com/wiki/Category:Tools::QtCreator}
{\QC Development Wiki}.
\section2 Running on Symbian Emulator
Select the \gui{Symbian Emulator} target as the active one, and build and
run your project.
If you cannot run the application in the emulator, check that:
\list
\o You selected the \gui{Symbian Emulator} target for your application.
\o If you cannot select \gui {Symbian Emulator} as target, check that
Carbide.c++ is installed correctly and that the path to the
Carbide.c++ installation directory is specified for the WINSCW tool
chain in the \gui{Compiler path} field in \gui {Tools > Options >
Tool Chains}.
\o If the emulator process cannot be started, try closing \QC and
starting the application directly from your file manager. Having
done this, \QC should be able to run your projects in the emulator.
\endlist

View File

@@ -1,31 +0,0 @@
\section2 Specifying Run Settings for Symbian Devices
\QC automatically detects Symbian devices that are connected to the
development PC with a USB cable. If only one device is detected, the
application is deployed to it and run on it. If multiple devices are
connected to the PC, make sure that the correct device is selected in the
\gui {Symbian Device} run settings for your project.
You can also pass command line arguments to your application on the device.
Press the \gui{Device info button} to get more information about the
selected device, such as the CPU type and the running debugging agent
version.
\image qtcreator-symbian-run-settings.png "Run settings for Symbian devices"
To use the CODA debugging agent over a WLAN connection, enter the WLAN
address of the device and the port number to use, separated by a colon (:),
in the \gui WLAN field. For example: 192.167.0.100:1534
When you deploy the application for the \gui{Symbian Device} target, \QC
generates a Symbian installation system (SIS) file in the project folder
and copies it to the device that is connected to the development PC. If no
device is connected, you must remove the \gui {Deploy SIS Package} step
to create the package. Click \gui {Remove Item} (1) to skip the step.
\image qtcreator-remove-deploy-step.png "Removing deploy steps"
When you are ready to publish the application to Nokia Store or some other
channel, you must make sure that the SIS file meets the requirements for
publishing and installing applications on Symbian devices. For more
information, see \l{Deploying Applications to Symbian Devices}.

View File

@@ -1,99 +0,0 @@
/****************************************************************************
**
** This file is part of Qt Creator
**
** Copyright (c) 2012 Nokia Corporation and/or its subsidiary(-ies).
**
** Contact: http://www.qt-project.org/
**
**
** 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 index.html
\previouspage creator-publish-ovi.html
\page creator-publish-ovi-symbian.html
\nextpage creator-publish-ovi-maemo.html
\title Publishing Qt Content for Symbian Devices
The \gui {Publish Qt Symbian Applications to Nokia Store} wizard allows you
to check that your application can be published to Nokia Store. It checks
that the application UID, vendor name, and the capabilities used meet the
\l{http://support.publish.nokia.com/?p=64}{Nokia Publish criteria}.
You can use the
\l{http://www.developer.nokia.com/Distribute/Packaging_and_signing.xhtml}
{Application Signing Services for Nokia Store} to get your application
Express Signed for free by Nokia. Submit an unsigned SIS file (with the
\l{Application UID}{application UID} that you receive from Nokia Publisher
Support) to the \l{https://publish.ovi.com/login}{Nokia Publish tool}.
If you use Symbian Signed UIDs or the application uses functions that
require advanced \l{Capabilities and Signing}{capabilities}, you must use
the standard Symbian Signed process to have the application Symbian Signed
(using the Certified Signed path or the manufacturer-specific channel).
For more information, see \l{Deploying Applications to Symbian Devices}.
To use the publishing wizard:
\list 1
\o Select \gui Projects to select the Qt version to build the
application. For more information, see
\l{Selecting Qt for Symbian Versions}.
\o Select the \gui {Symbian Device} build target for your project.
\o Choose \gui {Build > Publish Project}.
\o Select \gui {Publish Qt Symbian Applications to Nokia Store}, and then
select \gui {Start Wizard}.
\o Select the Qt version and device type to build against and click
\gui Next. We recommend that you select a release configuration.
\o The wizard checks the information in the project file against the
Nokia Publish criteria and indicates possible problems. You can fix
some of the problems in the wizard.
\image qtcreator-publishing-wizard-symbian.png "Project File Checks dialog"
\o Select \gui Commit to save changes and create the .sis file. The
.sis file is packaged with Nokia Smart Installer for Symbian.
\o Choose \gui {Open Containing Folder} to open the folder where the
.sis file was created.
\o Submit the created .sis file to Nokia Publish as a Qt Content item.
\endlist
\note After you change the application UID, you must use the developer
certificate-key pair that you receive from Nokia Publisher Support for testing
the application on devices. The following error message is displayed on the
device if you use UIDs from the trusted range (0x2xxxxxxx) in a self-signed
application: \gui {Unable to install a trusted application from a trusted
supplier.} For more
information, see \l{http://www.developer.nokia.com/Community/Wiki/UID}{UID}.
If you try to use more capabilites than the certificate permits, the
following error message is displayed on the device: \gui {Requested
application access not granted.} For example, if you try to install a
self-signed application that uses a system capability.
*/

View File

@@ -1,229 +0,0 @@
/****************************************************************************
**
** This file is part of Qt Creator
**
** Copyright (c) 2012 Nokia Corporation and/or its subsidiary(-ies).
**
** Contact: http://www.qt-project.org/
**
**
** 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 index.html
\previouspage creator-qml-application.html
\page creator-qml-components-example.html
\nextpage creator-writing-program.html
\title Using Qt Quick Components
\note To complete this tutorial, you must install the Qt Quick Components
for Symbian and the Symbian Anna target as part of the \QSDK. In addition,
you must install the Qt Quick Components on the test device.
This tutorial describes how to use \QC to create a small Qt
application, Battery Status, that uses the System Information
Mobility API to fetch battery information from the device.
\image qtcreator-symbian-components-example.png "Mobile example"
The user interface for the application is designed using Qt Quick Components
for Symbian. This enforces a platform look and feel for Symbian Anna devices.
\section1 Creating the Project
\list 1
\o Select \gui{File > New File or Project > Applications > Qt Quick
Application for Symbian > Choose}.
\o In the \gui{Name} field, type \bold {BatteryStatus}.
\o In the \gui {Create in} field, enter the path for the project files.
For example, \c {C:\Qt\examples}, and then click \gui{Next}.
\o Select \gui {Symbian Device} and \gui {\QS} targets, and
then click \gui{Next}.
\note Targets are listed if you installed the appropriate
development environment, for example, as part of the \QSDK. You can
add targets later in the \gui Projects mode.
\o Select \gui Next in the following dialogs to use the default
settings.
\note \QC contains a default program icon and generates an
\l{Application UID}, for testing the application on a device. You
only need to change the icon and UID if you deliver the application
for public use.
\o Review the project settings, and click \gui{Finish} to create the
project.
\endlist
\QC generates the necessary files that contain boiler plate code. The
wizard creates an application that uses
\l{http://doc.qt.nokia.com/qt-components-symbian/qt-components-pages-and-navigation-overview.html}
{page-based application navigation}.
Modify the files as described in the following sections.
\section1 Declaring the Qt Mobility API
To use the Qt Mobility APIs or develop applications for Symbian devices,
you must modify the .pro file to declare the Qt Mobility APIs that you use.
This example uses the System Info API, so you must declare it, as
illustrated by the following code snippet:
\code
CONFIG += mobility
MOBILITY = systeminfo
\endcode
Each Mobility API has its corresponding value that you have to add
as a value of MOBILITY to use the API. For a list of the APIs and the
corresponding values that you can assign to MOBILITY, see the
\l {http://doc.qt.nokia.com/qtmobility/quickstart.html}{Quickstart Example}.
\section1 Adding Import Statements
The wizard adds the import statements for Qt Quick and the Qt Quick
Components for Symbian to the MainPage.qml file:
\snippet examples/batterystatus/qml/BatteryStatus/MainPage.qml 3
To use the Qt Mobility APIs, you must add the import statements for the
Qt Mobility APIs that you use. This example uses the System Info API, so you
must import it, as illustrated by the following code snippet:
\snippet examples/batterystatus/qml/BatteryStatus/MainPage.qml 4
Use the values as you can assign to MOBILITY also to construct import
statements.
\section1 Creating the Main View
Qt Creator generates a default QML file that you can modify to create the
main view of the application. It displays a progress bar and a text label
that indicate the battery status.
\list 1
\o Click \gui Design to open MainPage.qml in \QMLD.
\o In the \gui Navigator pane, select the \gui Text element to edit its
properties in the \gui Properties pane.
\o In the \gui Text field, change the text from \bold {Hello World!}
to \gui {Battery status: 1%}.
\o In the \gui Library view, \gui Items tab, select the
\gui ProgressBar element, drag and drop it to the canvas, and edit
its properties.
\image qtcreator-symbian-components-example-ui.png "Qt Quick Components for Symbian"
\list 1
\o Click \gui {Layout}, and then click the top anchor button.
\o In the \gui Target field, select \gui text1, to anchor the
progress bar to the bottom of the text field.
\o In the \gui Margin field, select 20.
\o Click the horizontal anchor button, and select \gui text1 in
the \gui Target field to anchor the progress bar
horizontally to the text field.
\o To check that the application can be built and run, select
\gui {\QS} as the target and click the
\inlineimage qtcreator-run.png
button.
\endlist
\endlist
\section1 Fetching Battery Status
To fetch the battery status, open MainPage.qml in the code editor and add
some code to it:
\list 1
\o Add an invisible
\l{http://doc.qt.nokia.com/qtmobility/qml-deviceinfo.html}
{DeviceInfo element} that sets the
\l{http://doc.qt.nokia.com/qtmobility/qml-deviceinfo.html}
{monitorBatteryLevelChanges} property to true. It uses the
\c monitorBatteryLevelChanges signal to keep up with changes in the
battery level.
\snippet examples/batterystatus/qml/BatteryStatus/MainPage.qml 0
\o Set an expression as the value of the text property of the Text
element to display the battery level as a percentage:
\snippet examples/batterystatus/qml/BatteryStatus/MainPage.qml 1
\o Set values for the ProgressBar element to display the battery level
on the progress bar:
\snippet examples/batterystatus/qml/BatteryStatus/MainPage.qml 2
\endlist
\section1 Compiling and Running Your Program
Now that you have all the necessary code, select \gui {\QS}
as the target and click the
\inlineimage qtcreator-run.png
button to build your program and run it in \QS.
In \QS, run the runOutOfBattery.qs example script to see the value
change in the Battery Status application. Select \gui {Scripting > examples
> runOutOfBattery.qs > Run Selected Script}.
\image qtcreator-symbian-components-example-simulated.png "Mobile example in Qt Simulator"
\section1 Testing on a Symbian Device
You also need to test the application on real devices. Before you can
start testing on Symbian devices, you must connect them to the development
PC by using a USB cable and install the necessary software on them.
\list 1
\o Install Qt libraries, Qt mobile libraries, Qt Quick components for
Symbian, and a debugging agent on the device. For more information,
see \l{Connecting Symbian Devices}.
\o Start the CODA debugging agent on the device.
\o Click the \gui {Target Selector} and select \gui {Symbian Device}.
\o Click \gui Run to build the application for the Symbian device.
\endlist
*/

View File

@@ -1,310 +0,0 @@
/****************************************************************************
**
** This file is part of Qt Creator
**
** Copyright (c) 2012 Nokia Corporation and/or its subsidiary(-ies).
**
** Contact: http://www.qt-project.org/
**
**
** 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 index.html
\if defined(qcmanual)
\previouspage creator-developing-maemo.html
\else
\previouspage sdk-gs.html
\endif
\page creator-developing-symbian.html
\if defined(qcmanual)
\nextpage creator-developing-qnx.html
\else
\nextpage creator-developing-meego.html
\endif
\title Connecting Symbian Devices
When you install \QSDK, the build and run settings for Symbian devices
are set up automatically in \QC. You only need to install and launch
the \l{Using On-device Debugging Agents}{CODA on-device debugging agent}
on the devices and connect the devices to the development PC.
Make sure that \l{http://www.nokia.com/ovisuite}{Ovi Suite} or
\l{http://www.nokia.com/pcsuite}{PC Suite} is installed on the development PC.
Connect the device to the development PC with an USB cable in
Ovi Suite or PC Suite Mode. This setting is in the device USB settings.
If you have not previously used the device with Ovi Suite
or PC Suite, all the necessary drivers are installed automatically.
This takes approximately one minute.
You can run Qt applications on Symbian devices if the software that Qt
applications require (typically Qt, Qt Mobility, QtWebkit, and Open C) is
installed on the device. On Symbian Anna and later devices, some version of Qt
is pre-installed. For more information, see
\l{http://developer.qt.nokia.com/wiki/Support_for_Symbian#4ebe3e7733f9c23c76ac25559fc814a1}
{Device Configurations}.
To deploy applications to earlier devices, you can package
the application with Nokia Smart Installer for Symbian to automatically
install the modules that Qt applications require. For more information about
which Qt modules are supported on-demand for different Symbian device
models, see
\l{http://www.developer.nokia.com/Community/Wiki/Nokia_Smart_Installer_for_Symbian}
{Nokia Smart Installer for Symbian}.
The tool chain for building applications locally on the development PC for
the \gui {Symbian Device} target is only supported on Windows.
If you develop on Linux or Mac OS, you must use the Remote Compiler
interface to a compilation service at Nokia Developer. You can install
Remote Compiler as part of the \QSDK. For more information, see
\if defined(qcmanual)
\l{Building with Remote Compiler}.
\else
\l{http://doc.qt.nokia.com/qtcreator/creator-remote-compiler.html}
{Building with Remote Compiler}.
\endif
For more information about developing applications for the Symbian
platform, select \gui {Help > Index} and look for \gui {Platform Notes},
or see
\l{http://doc.qt.nokia.com/4.8/platform-notes-symbian.html}
{Platform Notes - Symbian}.
\section1 Using On-device Debugging Agents
To run and debug applications on Symbian devices from \QC, you must
install the CODA on-device debugging agent on the device.
Support for the App TRK on-device debugging agent has been removed from
\QC 2.3. Only CODA is supported Qt SDK 1.1.3 onward. It offers the following
benefits:
\list
\o Extensive error information
\o Debugging over WLAN
\o Extensive information about the device
\endlist
\note CODA does not support debugging over a Bluetooth connection.
\section2 Installing Debugging Agents
The CODA installation package is delivered together with \QSDK. You can
find it in the \QSDK installation folder in the
\c{\Symbian\sis\<target>\CODA} folder. On Windows, you can use \gui Start
menu commands to install CODA on Symbian devices.
\section1 Setting Up Qt Creator
When you run \QC after installing the Symbian SDK and Qt for
Symbian, the installed SDKs and their corresponding Qt versions are
automatically detected. For each detected Symbian SDK with Qt, a special entry
is made in the Qt version management settings in \gui{Tools} >
\gui{Options} > \gui{Build & Run} > \gui{Qt Versions}.
If you manually add a Qt version for Symbian, you must
also manually specify the Symbian SDK to use for this version.
For more information about adding Qt versions and tool chains, see
\if defined(qcmanual)
\l{Setting Up Qt for Symbian Versions} and \l{Adding Tool Chains}.
\else
\l{http://doc.qt.nokia.com/qtcreator/creator-project-qmake.html#setting-up-qt-for-symbian-versions}
{Setting Up Qt for Symbian Versions} and
\l{http://doc.qt.nokia.com/qtcreator/creator-tool-chains.html}
{Adding Tool Chains}.
\endif
\section1 Building and Running Applications
You can test your application on a device by building and running
it from \QC for the \gui {Symbian Device} target.
\list 1
\o Connect the device to the development PC through a USB cable.
The target selector displays a green check mark when a
device is connected.
\image qtcreator-qt4-symbian-device-connected.png
The tool tip of the target selector shows more details about the actual
device that will be used when you run your application.
\o Start the CODA debugging agent on the device.
\o Select \gui Options to select USB as connection type.
\o Click \gui Projects to edit the \gui {Build Settings} for the
\gui {Symbian Device} target. Select the Qt version to use for building
the application. For more information, see
\l{Selecting Qt for Symbian Versions}.
\o Click the \gui Run button in \QC.
\endlist
\section2 Selecting Qt for Symbian Versions
When you select the Qt for Symbian version to build the application with, consider
which version provides the application with the widest support on different
Symbian platforms. The binary compatibility promise of Qt and Symbian means
that applications that are built against Qt 4.6.3 also run on Qt 4.7.3.
Similarly, applications that are supported on S60 5th Edition are also
supported
on Symbian Anna and Belle. However, dependencies, such as Qt Quick or Qt Mobility API
versions might restrict the choice of Qt versions that you have.
If you use Qt Quick in the application, you can use \gui {S60 5th Edition
Qt 4.7.3} to build it. The application is supported on both S60 5th Edition
and Symbian Anna and Belle devices. However, if you only target Symbian
Anna and Belle, you can use the state of art Qt in the \gui {Symbian Anna
Qt 4.7.4} target to build the application. This allows you to re-use the
application for MeeGo Harmattan devices.
If you want to use the native Symbian Belle APIs and make sure that the
application created for earlier Symbian platforms work on Belle as well,
use \gui {Symbian Belle Qt 4.7.4} to build them. You cannot run such
applications on Symbian Anna or earlier Symbian platforms.
\note The \QSDK only contains the latest tool chains available for
developing applications for a particular Symbian platform. The Qt 4.6.3 for
Symbian and Qt 4.7.3 for Symbian^3 and Symbian Anna targets have been
removed from \QSDK 1.1.4. To develop for those targets, use \QSDK 1.1.2.
If you use native Symbian APIs, you must check that they are available on
the target devices. For more information about the API differences between
Symbian platforms, see the \bold {Symbian
Reference Documentation for Qt}, which is delivered together with \QSDK
and which you can view in the \gui Help mode.
You can use a set of ready-made UI components called Qt Quick Components
for Symbian that enforce a Nokia UI look and feel. \QSDK updates the Qt
Quick Components to version 1.1 that contains usability and other
improvements. All devices that support Qt Quick Components for Symbian
support version 1.1.
The following table summarizes the supported configurations for each Qt
version available in \QC build settings:
\table
\header
\o Qt Version
\o Qt Quick
\o Qt Quick Components
\o Qt Mobility Version
\o Native Symbian C++ APIs
\o Qt OpenGL Support
\row
\o S60 5th Edition Qt 4.7.3 (online installer only)
\o 1.0
\o No
\o 1.1.3
\o No
\o No
\row
\o Symbian Anna Qt 4.7.4
\o 1.1
\o 1.1
\o 1.2
\o Yes (Symbian Anna APIs)
\o Yes
\row
\o Symbian Belle Qt 4.7.4 (online installer only)
\o 1.1
\o 1.1
\o 1.2
\o Yes (Symbian Belle APIs)
\o Yes
\endtable
\section2 Developing Applications Using Qt 4.6.3 or Qt 4.7.3 for Symbian
S60 3rd Edition devices support only Qt 4.6.3, not Qt 4.7 or later. Further,
support for the App TRK on-device debugging agent has been removed from
\QC 2.3. Only CODA is supported from Qt SDK 1.1.3 onward, and CODA does not
support S60 3rd Edition. Therefore, you can no longer run and debug
applications from \QC on S60 3rd Edition devices.
The tool chains for developing applications using Qt 4.6.3 for Symbian
and Qt 4.7.3 for Symbian^ 3 and Symbian Anna have been removed from \QSDK
1.1.4. To develop such applications,
\l{http://qt.nokia.com/downloads/downloads}
{download and use \QSDK version 1.1.2} instead. It contains Qt 4.6.3 for
Symbian and Qt 4.7.4 for Symbian support for Symbian devices with
the Application TRK debug agent.
\note Problems may arise if you install multiple instances of Qt SDK on the
same development PC using the same user account. Use separate user accounts
to install them or install them on separate development PCs.
\note Do not update \QSDK 1.1.2 with the \QSDK update tool, because
the updater removes App TRK support.
In general, if you use only Qt 4.6 APIs in the application, you
can use \gui {S60 5th Edition Qt 4.6.3} to build it. The application is
supported on both S60 5th Edition and later devices.
The following table summarizes the supported configurations for each Qt
version available in \QC build settings if you installed \QSDK 1.1.2.
\table
\header
\o Qt Version
\o Qt Quick
\o Qt Quick Components
\o Qt Mobility Version
\o Native Symbian C++ APIs
\o Qt OpenGL Support
\row
\o Qt 4.6.3 for Symbian^1 (S60 5th Edition)
\o No
\o No
\o 1.0.2
\o No
\o No
\row
\o Qt 4.6.3 for Symbian^3
\o No
\o No
\o 1.0.2
\o Yes (Symbian^3 APIs)
\o No
\row
\o Qt 4.7.3 for Symbian^3 and Symbian Anna
\o 1.0
\o 1.0
\o 1.1.3
\o Yes (Symbian Anna APIs)
\o Yes
\endtable
\section1 Advanced Development with Symbian SDK
For normal Qt application development, \QSDK provides all you need even if
the application needs native Symbian OS API access.
However, for more advanced Symbian application development, Nokia provides
the \l{http://www.developer.nokia.com/carbide_cpp}{Carbide C++ IDE} and
\l{http://www.developer.nokia.com/Resources/Tools_and_downloads/Other/Symbian_SDKs/}
{Symbian C++ SDKs}. You can use them also for Qt application development.
For example, these SDKs provide Symbian device emulators that are built
mostly from the software that the actual devices are running. Therefore,
they provide much closer emulation of the device than \QS.
*/

View File

@@ -25,7 +25,6 @@
/*! /*!
\contentspage index.html \contentspage index.html
\previouspage creator-qml-components-example.html
\page creator-writing-program.html \page creator-writing-program.html
\nextpage creator-project-managing.html \nextpage creator-project-managing.html

View File

@@ -1,11 +1,7 @@
TEMPLATE = subdirs # XXX: Avoid call the linker TEMPLATE = subdirs # XXX: Avoid call the linker
TARGETPATH = Qt/labs/components/custom TARGETPATH = Qt/labs/components/custom
symbian { INSTALL_IMPORTS = $$[QT_INSTALL_IMPORTS]
INSTALL_IMPORTS = /resource/qt/imports
} else {
INSTALL_IMPORTS = $$[QT_INSTALL_IMPORTS]
}
QML_FILES = \ QML_FILES = \
qmldir \ qmldir \
@@ -43,7 +39,3 @@ lessThan(QT_MAJOR_VERSION, 5):qmldirs.sources = $$QML_DIRS
qmldirs.path = $$INSTALL_IMPORTS/$$TARGETPATH qmldirs.path = $$INSTALL_IMPORTS/$$TARGETPATH
INSTALLS += qmlfiles qmldirs INSTALLS += qmlfiles qmldirs
symbian {
DEPLOYMENT += qmlfiles qmldirs
}

View File

@@ -22,7 +22,6 @@ Project {
"src/libs/qmljs/qmljs.qbs", "src/libs/qmljs/qmljs.qbs",
"src/libs/qmldebug/qmldebug.qbs", "src/libs/qmldebug/qmldebug.qbs",
"src/libs/qtcomponents/styleitem/styleitem.qbs", "src/libs/qtcomponents/styleitem/styleitem.qbs",
"src/libs/symbianutils/symbianutils.qbs",
"src/libs/ssh/ssh.qbs", "src/libs/ssh/ssh.qbs",
"src/libs/utils/process_stub.qbs", "src/libs/utils/process_stub.qbs",
"src/libs/utils/process_ctrlc_stub.qbs", "src/libs/utils/process_ctrlc_stub.qbs",

View File

@@ -2211,39 +2211,6 @@ def qdump__boost__posix_time__time_duration(d, item):
d.putNumChild(0) d.putNumChild(0)
#######################################################################
#
# Symbian
#
#######################################################################
def encodeSymbianString(base, size):
s = ""
for i in xrange(size):
val = int(base[i])
if val == 9:
s += "5c007400" # \t
else:
s += "%02x%02x" % (val % 256, val / 256)
return s
def qdump__TBuf(d, value):
size = value["iLength"] & 0xffff
base = value["iBuf"]
max = numericTemplateArgument(value.type, 0)
check(0 <= size and size <= max)
d.putNumChild(0)
d.putValue(encodeSymbianString(base, size), Hex4EncodedLittleEndian)
def qdump__TLitC(d, value):
size = value["iTypeLength"] & 0xffff
base = value["iBuf"]
max = numericTemplateArgument(value.type, 0)
check(0 <= size and size <= max)
d.putNumChild(0)
d.putValue(encodeSymbianString(base, size), Hex4EncodedLittleEndian)
####################################################################### #######################################################################
# #
# SSE # SSE

View File

@@ -4,20 +4,11 @@
QT += declarative script QT += declarative script
INCLUDEPATH += $$PWD/include INCLUDEPATH += $$PWD/include
symbian { windows:CONFIG(debug, debug|release) {
LIBNAME = QmlJSDebugger.lib LIBNAME = QmlJSDebuggerd
} else { } else {
windows:CONFIG(debug, debug|release) { LIBNAME = QmlJSDebugger
LIBNAME = QmlJSDebuggerd
} else {
LIBNAME = QmlJSDebugger
}
} }
LIBS += -L$$PWD -l$$LIBNAME LIBS += -L$$PWD -l$$LIBNAME
symbian {
# Work around bug in gcce toolchain (QTCREATORBUG-5589)
LIBS += -lusrt2_2.lib
}
DEFINES += QMLJSDEBUGGER DEFINES += QMLJSDEBUGGER

View File

@@ -19,11 +19,7 @@ SOURCES += $$PWD/qmlruntime.cpp \
RESOURCES = $$PWD/browser/browser.qrc \ RESOURCES = $$PWD/browser/browser.qrc \
$$PWD/startup/startup.qrc $$PWD/startup/startup.qrc
symbian:!contains(S60_VERSION, 3.1):!contains(S60_VERSION, 3.2) { maemo5 {
SOURCES += $$PWD/deviceorientation_symbian.cpp
FORMS = $$PWD/recopts.ui \
$$PWD/proxysettings.ui
} else:maemo5 {
QT += dbus QT += dbus
HEADERS += $$PWD/texteditautoresizer_maemo5.h HEADERS += $$PWD/texteditautoresizer_maemo5.h
SOURCES += $$PWD/deviceorientation_maemo5.cpp SOURCES += $$PWD/deviceorientation_maemo5.cpp

View File

@@ -8,20 +8,6 @@ DEPLOYMENTFOLDERS = folder_01
# TOUCH_OPTIMIZED_NAVIGATION # # TOUCH_OPTIMIZED_NAVIGATION #
DEFINES += TOUCH_OPTIMIZED_NAVIGATION DEFINES += TOUCH_OPTIMIZED_NAVIGATION
# TARGETUID3 #
symbian:TARGET.UID3 = 0xE1111234
# Allow network access on Symbian
# NETWORKACCESS #
symbian:TARGET.CAPABILITY += NetworkServices
# 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
# If your application uses the Qt Mobility libraries, uncomment the following # If your application uses the Qt Mobility libraries, uncomment the following
# lines and add the respective components to the MOBILITY variable. # lines and add the respective components to the MOBILITY variable.
# CONFIG += mobility # CONFIG += mobility

View File

@@ -140,17 +140,6 @@ void Html5ApplicationViewer::loadUrl(const QUrl &url)
void Html5ApplicationViewer::setOrientation(ScreenOrientation orientation) void Html5ApplicationViewer::setOrientation(ScreenOrientation orientation)
{ {
#if defined(Q_OS_SYMBIAN)
// If the version of Qt on the device is < 4.7.2, that attribute won't work
if (orientation != ScreenOrientationAuto) {
const QStringList v = QString::fromLatin1(qVersion()).split(QLatin1Char('.'));
if (v.count() == 3 && (v.at(0).toInt() << 16 | v.at(1).toInt() << 8 | v.at(2).toInt()) < 0x040702) {
qWarning("Screen orientation locking only supported with Qt 4.7.2 and above");
return;
}
}
#endif // Q_OS_SYMBIAN
Qt::WidgetAttribute attribute; Qt::WidgetAttribute attribute;
switch (orientation) { switch (orientation) {
#if QT_VERSION < 0x040702 #if QT_VERSION < 0x040702
@@ -183,9 +172,7 @@ void Html5ApplicationViewer::setOrientation(ScreenOrientation orientation)
void Html5ApplicationViewer::showExpanded() void Html5ApplicationViewer::showExpanded()
{ {
#if defined(Q_OS_SYMBIAN) || defined(Q_WS_SIMULATOR) #if defined(Q_WS_MAEMO_5)
showFullScreen();
#elif defined(Q_WS_MAEMO_5)
showMaximized(); showMaximized();
#else #else
show(); show();

View File

@@ -31,7 +31,7 @@ public:
void loadFile(const QString &fileName); void loadFile(const QString &fileName);
void loadUrl(const QUrl &url); void loadUrl(const QUrl &url);
// Note that this will only have an effect on Symbian and Fremantle. // Note that this will only have an effect on Fremantle.
void setOrientation(ScreenOrientation orientation); void setOrientation(ScreenOrientation orientation);
void showExpanded(); void showExpanded();

View File

@@ -70,7 +70,7 @@ QPoint closestElement(QObject *viewObject, QWebFrame *frame, WebTouchEvent &touc
} }
// QtWebKit EditorClientQt already enables these input hints. Thus, this should only be // QtWebKit EditorClientQt already enables these input hints. Thus, this should only be
// enabled if QtWebKit happens to be old. Qt::ImhNoPredictiveText is only enalbed for Symbian / Maemo on WebKit side. // enabled if QtWebKit happens to be old. Qt::ImhNoPredictiveText is only enalbed for Maemo on WebKit side.
touchEvent.m_editable = true; touchEvent.m_editable = true;

View File

@@ -4,20 +4,6 @@
# dir1.source = mydir # dir1.source = mydir
DEPLOYMENTFOLDERS = # file1 dir1 DEPLOYMENTFOLDERS = # file1 dir1
# TARGETUID3 #
symbian:TARGET.UID3 = 0xE1111234
# 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
# NETWORKACCESS #
symbian:TARGET.CAPABILITY += NetworkServices
# If your application uses the Qt Mobility libraries, uncomment # If your application uses the Qt Mobility libraries, uncomment
# the following lines and add the respective components to the # the following lines and add the respective components to the
# MOBILITY variable. # MOBILITY variable.

View File

@@ -16,17 +16,6 @@ MainWindow::~MainWindow()
void MainWindow::setOrientation(ScreenOrientation orientation) void MainWindow::setOrientation(ScreenOrientation orientation)
{ {
#if defined(Q_OS_SYMBIAN)
// If the version of Qt on the device is < 4.7.2, that attribute won't work
if (orientation != ScreenOrientationAuto) {
const QStringList v = QString::fromLatin1(qVersion()).split(QLatin1Char('.'));
if (v.count() == 3 && (v.at(0).toInt() << 16 | v.at(1).toInt() << 8 | v.at(2).toInt()) < 0x040702) {
qWarning("Screen orientation locking only supported with Qt 4.7.2 and above");
return;
}
}
#endif // Q_OS_SYMBIAN
Qt::WidgetAttribute attribute; Qt::WidgetAttribute attribute;
switch (orientation) { switch (orientation) {
#if QT_VERSION < 0x040702 #if QT_VERSION < 0x040702
@@ -59,7 +48,7 @@ void MainWindow::setOrientation(ScreenOrientation orientation)
void MainWindow::showExpanded() void MainWindow::showExpanded()
{ {
#if defined(Q_OS_SYMBIAN) || defined(Q_WS_SIMULATOR) #if defined(Q_WS_SIMULATOR)
showFullScreen(); showFullScreen();
#elif defined(Q_WS_MAEMO_5) #elif defined(Q_WS_MAEMO_5)
showMaximized(); showMaximized();

View File

@@ -20,7 +20,7 @@ public:
explicit MainWindow(QWidget *parent = 0); explicit MainWindow(QWidget *parent = 0);
virtual ~MainWindow(); virtual ~MainWindow();
// Note that this will only have an effect on Symbian and Fremantle. // Note that this will only have an effect on Fremantle.
void setOrientation(ScreenOrientation orientation); void setOrientation(ScreenOrientation orientation);
void showExpanded(); void showExpanded();

View File

@@ -9,20 +9,6 @@ DEPLOYMENTFOLDERS = folder_01
# QML_IMPORT_PATH # # QML_IMPORT_PATH #
QML_IMPORT_PATH = QML_IMPORT_PATH =
# TARGETUID3 #
symbian:TARGET.UID3 = 0xE1111234
# 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
# NETWORKACCESS #
symbian:TARGET.CAPABILITY += NetworkServices
# If your application uses the Qt Mobility libraries, uncomment the following # If your application uses the Qt Mobility libraries, uncomment the following
# lines and add the respective components to the MOBILITY variable. # lines and add the respective components to the MOBILITY variable.
# CONFIG += mobility # CONFIG += mobility
@@ -32,10 +18,6 @@ symbian:TARGET.CAPABILITY += NetworkServices
# HARMATTAN_BOOSTABLE # # HARMATTAN_BOOSTABLE #
# CONFIG += qdeclarative-boostable # CONFIG += qdeclarative-boostable
# Add dependency to Symbian components
# QTQUICKCOMPONENTS #
# CONFIG += qt-components
# The .cpp file which was generated for your project. Feel free to hack it. # The .cpp file which was generated for your project. Feel free to hack it.
SOURCES += main.cpp SOURCES += main.cpp

View File

@@ -1,4 +1,3 @@
// import QtQuick 1.0 // to target S60 5th Edition or Maemo 5
import QtQuick 1.1 import QtQuick 1.1
Rectangle { Rectangle {

View File

@@ -1,12 +0,0 @@
import QtQuick 1.1
import com.nokia.symbian 1.1
Page {
id: mainPage
Text {
anchors.centerIn: parent
text: qsTr("Hello world!")
color: platformStyle.colorNormalLight
font.pixelSize: 20
}
}

View File

@@ -1,18 +0,0 @@
import QtQuick 1.1
import com.nokia.symbian 1.1
PageStackWindow {
id: window
initialPage: MainPage {tools: toolBarLayout}
showStatusBar: true
showToolBar: true
ToolBarLayout {
id: toolBarLayout
ToolButton {
flat: true
iconSource: "toolbar-back"
onClicked: window.pageStack.depth <= 1 ? Qt.quit() : window.pageStack.pop()
}
}
}

View File

@@ -117,17 +117,6 @@ void QmlApplicationViewer::addImportPath(const QString &path)
void QmlApplicationViewer::setOrientation(ScreenOrientation orientation) void QmlApplicationViewer::setOrientation(ScreenOrientation orientation)
{ {
#if QT_VERSION < 0x050000 #if QT_VERSION < 0x050000
#if defined(Q_OS_SYMBIAN)
// If the version of Qt on the device is < 4.7.2, that attribute won't work
if (orientation != ScreenOrientationAuto) {
const QStringList v = QString::fromLatin1(qVersion()).split(QLatin1Char('.'));
if (v.count() == 3 && (v.at(0).toInt() << 16 | v.at(1).toInt() << 8 | v.at(2).toInt()) < 0x040702) {
qWarning("Screen orientation locking only supported with Qt 4.7.2 and above");
return;
}
}
#endif // Q_OS_SYMBIAN
Qt::WidgetAttribute attribute; Qt::WidgetAttribute attribute;
switch (orientation) { switch (orientation) {
#if QT_VERSION < 0x040702 #if QT_VERSION < 0x040702
@@ -163,7 +152,7 @@ void QmlApplicationViewer::setOrientation(ScreenOrientation orientation)
void QmlApplicationViewer::showExpanded() void QmlApplicationViewer::showExpanded()
{ {
#if defined(Q_OS_SYMBIAN) || defined(MEEGO_EDITION_HARMATTAN) || defined(Q_WS_SIMULATOR) #if defined(MEEGO_EDITION_HARMATTAN) || defined(Q_WS_SIMULATOR)
showFullScreen(); showFullScreen();
#elif defined(Q_WS_MAEMO_5) #elif defined(Q_WS_MAEMO_5)
showMaximized(); showMaximized();

View File

@@ -31,7 +31,7 @@ public:
void setMainQmlFile(const QString &file); void setMainQmlFile(const QString &file);
void addImportPath(const QString &path); void addImportPath(const QString &path);
// Note that this will only have an effect on Symbian and Fremantle. // Note that this will only have an effect on Fremantle.
void setOrientation(ScreenOrientation orientation); void setOrientation(ScreenOrientation orientation);
void showExpanded(); void showExpanded();

View File

@@ -1,5 +1,5 @@
# This file was generated by an application wizard of Qt Creator. # This file was generated by an application wizard of Qt Creator.
# The code below handles deployment to Symbian and Maemo, aswell as copying # The code below handles deployment to Android and Maemo, aswell as copying
# of the application data to shadow build directories on desktop. # of the application data to shadow build directories on desktop.
# It is recommended not to modify this file, since newer versions of Qt Creator # It is recommended not to modify this file, since newer versions of Qt Creator
# may offer an updated version of it. # may offer an updated version of it.
@@ -22,10 +22,7 @@ for(deploymentfolder, DEPLOYMENTFOLDERS) {
MAINPROFILEPWD = $$PWD MAINPROFILEPWD = $$PWD
symbian { android {
isEmpty(ICON):exists($${TARGET}.svg):ICON = $${TARGET}.svg
isEmpty(TARGET.EPOCHEAPSIZE):TARGET.EPOCHEAPSIZE = 0x20000 0x2000000
} else:android {
for(deploymentfolder, DEPLOYMENTFOLDERS) { for(deploymentfolder, DEPLOYMENTFOLDERS) {
item = item$${deploymentfolder} item = item$${deploymentfolder}
itemfiles = $${item}.files itemfiles = $${item}.files

View File

@@ -1,93 +0,0 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
height="44px"
version="1.1"
viewBox="0 0 44 44"
width="44px"
x="0px"
y="0px"
id="svg2"
inkscape:version="0.47 r22583"
sodipodi:docname="qt.svg">
<metadata
id="metadata18">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
</cc:Work>
</rdf:RDF>
</metadata>
<defs
id="defs16">
<inkscape:perspective
sodipodi:type="inkscape:persp3d"
inkscape:vp_x="0 : 22 : 1"
inkscape:vp_y="0 : 1000 : 0"
inkscape:vp_z="44 : 22 : 1"
inkscape:persp3d-origin="22 : 14.666667 : 1"
id="perspective2836" />
</defs>
<sodipodi:namedview
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1"
objecttolerance="10"
gridtolerance="10"
guidetolerance="10"
inkscape:pageopacity="0"
inkscape:pageshadow="2"
inkscape:window-width="1920"
inkscape:window-height="1020"
id="namedview14"
showgrid="false"
inkscape:zoom="21.454545"
inkscape:cx="49.412871"
inkscape:cy="21.894358"
inkscape:window-x="-4"
inkscape:window-y="-4"
inkscape:window-maximized="1"
inkscape:current-layer="g3" />
<g
transform="matrix(0.18308778,0,0,0.18308778,6.6100946,3.2385199)"
id="g3">
<path
d="M 43.09,0.3586 C 40.94,0.0036 38.84,-0.0824 36.81,0.0776 31.968136,0.39505671 27.122677,0.73638425 22.28,1.0696 9.62,2.0816 0,12.4996 0,26.8896 l 0,169.7 14.19,13.2 28.87,-209.42 0.03,-0.011 z"
style="fill:#006225"
id="path5"
sodipodi:nodetypes="cccccccc" />
<path
d="m 174.4,160 c 0,12.5 -7.75,24.07 -17.57,25.77 L 14.23,209.73 V 25.93 C 14.23,9.21 27.57,-2.27 43.12,0.3 l 131.3,21.52 v 138.2 z"
style="fill:#80c342"
id="path7" />
<path
d="m 154.9,80.96 -12.96,-0.598 0,0.278 6.945,0.32 6.016,0 z"
style="fill:#006225"
id="path11" />
<path
d="m 144.6,135.6 c 0.66,0.328 1.43,0.476 2.351,0.476 0.161,0 0.329,-0.004 0.497,-0.016 2.55,-0.148 5.32,-0.933 8.343,-2.308 h -6.015 c -1.821,0.832 -3.532,1.457 -5.176,1.848 z"
style="fill:#006225"
id="path13" />
<path
id="path17"
style="fill:#ffffff"
d="m 91.15,132.4 c 2.351,-6.051 3.511,-17.91 3.511,-35.62 0,-15.89 -1.148,-26.82 -3.484,-32.81 -2.336,-6.027 -5.832,-9.281 -10.52,-9.691 -0.359,-0.031 -0.714,-0.051 -1.058,-0.051 -4.34,0 -7.68,2.535 -10.01,7.625 -2.52,5.543 -3.793,17.04 -3.793,34.44 0,16.82 1.238,28.75 3.734,35.75 2.356,6.672 5.879,9.976 10.5,9.976 0.207,0 0.41,-0.008 0.621,-0.019 4.633,-0.293 8.121,-3.496 10.49,-9.602 m 17.98,3.75 c -4.117,9.707 -10.39,16.06 -18.99,19 0.867,4.449 2.176,7.441 3.922,9.019 1.351,1.211 3.433,1.821 6.222,1.821 0.805,0 1.668,-0.055 2.59,-0.157 v 13.12 l -5.961,0.782 c -1.758,0.23 -3.426,0.343 -5.004,0.343 -5.218,0 -9.445,-1.265 -12.62,-3.824 -4.207,-3.379 -7.308,-9.894 -9.297,-19.54 -9.136,-1.945 -16.26,-7.754 -21.19,-17.5 -5.004,-9.902 -7.551,-24.39 -7.551,-43.34 0,-20.43 3.484,-35.51 10.34,-45.07 5.789,-8.07 13.86,-12.04 24.02,-12.04 1.629,0 3.309,0.102 5.043,0.305 11.95,1.375 20.62,7.016 26.26,16.79 5.535,9.562 8.254,23.27 8.254,41.26 0,16.48 -2,29.45 -6.043,39.02 z M 130.4,45.91 l 11.52,1.238 0,20.21 12.96,0.914 0,12.68 -12.96,-0.598 0,46.33 c 0,4.032 0.445,6.625 1.34,7.789 0.8,1.067 2.046,1.594 3.71,1.594 0.161,0 0.329,-0.004 0.497,-0.016 2.55,-0.148 5.32,-0.933 8.343,-2.308 v 11.65 c -5.136,2.258 -10.18,3.598 -15.12,4.02 -0.718,0.055 -1.41,0.086 -2.078,0.086 -4.48,0 -7.906,-1.301 -10.25,-3.934 -2.73,-3.051 -4.09,-7.949 -4.09,-14.67 V 79.535 L 118.046,79.25 V 65.66 l 7.586,0.547 4.773,-20.3 z" />
<path
d="m 100.3,166 c 0.809,0 1.672,-0.055 2.59,-0.157 H 98.054 C 98.73,165.949 99.507,166 100.3,166 z"
style="fill:#006225"
id="path19" />
<path
id="path21"
style="fill:#006225"
d="m 84.85,63.98 c 2.336,5.997 3.484,16.92 3.484,32.81 0,17.7 -1.16,29.57 -3.512,35.62 -1.894,4.879 -4.527,7.902 -7.863,9.07 0.965,0.368 1.992,0.551 3.078,0.551 0.207,0 0.41,-0.008 0.621,-0.019 4.633,-0.293 8.121,-3.496 10.49,-9.602 2.351,-6.051 3.511,-17.91 3.511,-35.62 0,-15.89 -1.148,-26.82 -3.484,-32.81 -2.336,-6.027 -5.832,-9.281 -10.52,-9.691 -0.359,-0.031 -0.714,-0.051 -1.058,-0.051 -1.09,0 -2.117,0.16 -3.082,0.481 h -0.004 c 3.601,1.121 6.379,4.215 8.336,9.261 z m -2.344,114.3 c -0.113,-0.05 -0.227,-0.105 -0.336,-0.16 -0.012,-0.004 -0.023,-0.012 -0.035,-0.015 -0.102,-0.051 -0.207,-0.106 -0.309,-0.157 -0.019,-0.011 -0.039,-0.019 -0.058,-0.031 -0.09,-0.051 -0.184,-0.098 -0.278,-0.148 -0.027,-0.016 -0.054,-0.036 -0.086,-0.051 -0.082,-0.043 -0.164,-0.09 -0.242,-0.137 -0.039,-0.023 -0.078,-0.047 -0.113,-0.07 -0.07,-0.039 -0.145,-0.082 -0.215,-0.125 -0.047,-0.031 -0.094,-0.059 -0.14,-0.09 -0.059,-0.039 -0.118,-0.074 -0.176,-0.113 -0.059,-0.039 -0.114,-0.075 -0.168,-0.114 -0.051,-0.031 -0.102,-0.066 -0.149,-0.097 -0.066,-0.047 -0.132,-0.094 -0.195,-0.137 -0.039,-0.027 -0.078,-0.055 -0.113,-0.082 -0.078,-0.055 -0.153,-0.113 -0.231,-0.172 -0.023,-0.016 -0.05,-0.035 -0.078,-0.055 -0.098,-0.078 -0.199,-0.156 -0.297,-0.234 -4.207,-3.379 -7.308,-9.894 -9.297,-19.54 -9.136,-1.945 -16.26,-7.754 -21.19,-17.5 -5.004,-9.902 -7.551,-24.39 -7.551,-43.34 0,-20.43 3.484,-35.51 10.34,-45.07 5.789,-8.07 13.86,-12.04 24.02,-12.04 h -6.351 c -10.15,0.008 -18.22,3.977 -24,12.04 -6.855,9.563 -10.34,24.64 -10.34,45.07 0,18.95 2.547,33.44 7.551,43.34 4.934,9.75 12.05,15.56 21.19,17.5 1.989,9.641 5.09,16.16 9.297,19.54 3.176,2.559 7.403,3.824 12.62,3.824 0.098,0 0.199,0 0.297,-0.004 h 5.539 c -3.406,-0.05 -6.383,-0.66 -8.906,-1.828 L 82.498,178.28 z M 128.4,145.6 c -2.73,-3.051 -4.09,-7.949 -4.09,-14.67 V 79.57 l -6.226,-0.285 v -13.59 h -6.016 v 3.035 c 0.871,3.273 1.555,6.82 2.063,10.64 l 4.164,0.192 v 51.36 c 0,6.723 1.367,11.62 4.09,14.67 2.343,2.633 5.765,3.934 10.25,3.934 h 6.015 c -4.48,0 -7.906,-1.301 -10.25,-3.934 z m 2.043,-99.66 -6.016,0 -4.668,19.88 5.911,0.422 4.773,-20.3 z" />
</g>
</svg>

Before

Width:  |  Height:  |  Size: 6.4 KiB

View File

@@ -26,9 +26,7 @@ OTHER_FILES = qmldir
} }
qmldir.files = qmldir qmldir.files = qmldir
symbian { unix {
TARGET.EPOCALLOWDLLDATA = 1
} else:unix {
maemo5 | !isEmpty(MEEGO_VERSION_MAJOR) { maemo5 | !isEmpty(MEEGO_VERSION_MAJOR) {
installPath = /usr/lib/qt4/imports/$$replace(uri, \\., /) installPath = /usr/lib/qt4/imports/$$replace(uri, \\., /)
} else { } else {

View File

@@ -226,7 +226,6 @@ Product {
"deviceorientation.h", "deviceorientation.h",
"deviceorientation_harmattan.cpp", "deviceorientation_harmattan.cpp",
"deviceorientation_maemo5.cpp", "deviceorientation_maemo5.cpp",
"deviceorientation_symbian.cpp",
"loggerwidget.cpp", "loggerwidget.cpp",
"loggerwidget.h", "loggerwidget.h",
"main.cpp", "main.cpp",
@@ -918,16 +917,6 @@ Product {
] ]
} }
Group {
qbs.installDir: "share/qtcreator/templates/qtquickapp/qml/app/symbian11"
fileTags: ["install"]
prefix: "qtcreator/templates/qtquickapp/qml/app/symbian11/"
files: [
"MainPage.qml",
"main.qml",
]
}
Group { Group {
qbs.installDir: "share/qtcreator/templates/qtquickapp/qmlapplicationviewer" qbs.installDir: "share/qtcreator/templates/qtquickapp/qmlapplicationviewer"
fileTags: ["install"] fileTags: ["install"]
@@ -949,7 +938,6 @@ Product {
"icon64.png", "icon64.png",
"icon80.png", "icon80.png",
"manifest.aegis", "manifest.aegis",
"symbianicon.svg",
] ]
} }

View File

@@ -173,16 +173,6 @@ public:
} // end of anonymous namespace } // end of anonymous namespace
#ifdef Q_OS_SYMBIAN
//Symbian compiler has some difficulties to understand the templates.
static void delete_array_entries(std::vector<Symbol *> vt)
{
std::vector<Symbol *>::iterator it;
for (it = vt.begin(); it != vt.end(); ++it) {
delete *it;
}
}
#else
template <typename _Iterator> template <typename _Iterator>
static void delete_array_entries(_Iterator first, _Iterator last) static void delete_array_entries(_Iterator first, _Iterator last)
{ {
@@ -193,7 +183,6 @@ static void delete_array_entries(_Iterator first, _Iterator last)
template <typename _Array> template <typename _Array>
static void delete_array_entries(const _Array &a) static void delete_array_entries(const _Array &a)
{ delete_array_entries(a.begin(), a.end()); } { delete_array_entries(a.begin(), a.end()); }
#endif
class Control::Data class Control::Data
{ {

View File

@@ -9,7 +9,6 @@ SUBDIRS = \
utils \ utils \
utils/process_stub.pro \ utils/process_stub.pro \
languageutils \ languageutils \
symbianutils \
cplusplus \ cplusplus \
qmljs \ qmljs \
qmldebug \ qmldebug \

View File

@@ -1,3 +1 @@
include(../symbianutils/symbianutils.pri)
LIBS *= -l$$qtLibraryName(QmlDebug) LIBS *= -l$$qtLibraryName(QmlDebug)

View File

@@ -3,7 +3,6 @@ TARGET = QmlDebug
QT += network QT += network
include(../../qtcreatorlibrary.pri) include(../../qtcreatorlibrary.pri)
include(../symbianutils/symbianutils.pri)
include(qmldebug-lib.pri) include(qmldebug-lib.pri)
OTHER_FILES += \ OTHER_FILES += \

View File

@@ -14,7 +14,6 @@ QtcLibrary {
Depends { name: "cpp" } Depends { name: "cpp" }
Depends { name: "Qt"; submodules: ["gui", "network"] } Depends { name: "Qt"; submodules: ["gui", "network"] }
Depends { name: "symbianutils" }
files: [ files: [
"baseenginedebugclient.cpp", "baseenginedebugclient.cpp",
@@ -48,7 +47,6 @@ QtcLibrary {
ProductModule { ProductModule {
Depends { name: "cpp" } Depends { name: "cpp" }
Depends { name: "symbianutils" }
cpp.includePaths: ["."] cpp.includePaths: ["."]
} }
} }

View File

@@ -34,7 +34,6 @@
#include <qdebug.h> #include <qdebug.h>
#include <qstringlist.h> #include <qstringlist.h>
#include <qnetworkproxy.h> #include <qnetworkproxy.h>
#include <symbiandevicemanager.h>
namespace QmlDebug { namespace QmlDebug {
@@ -60,7 +59,7 @@ public:
QmlDebugConnectionPrivate(QmlDebugConnection *c); QmlDebugConnectionPrivate(QmlDebugConnection *c);
QmlDebugConnection *q; QmlDebugConnection *q;
QPacketProtocol *protocol; QPacketProtocol *protocol;
QIODevice *device; // Currently either a QTcpSocket or a SymbianUtils::OstChannel QIODevice *device; // Currently a QTcpSocket
bool gotHello; bool gotHello;
QHash <QString, float> serverPlugins; QHash <QString, float> serverPlugins;
@@ -295,18 +294,6 @@ QAbstractSocket::SocketState QmlDebugConnection::state() const
if (socket) if (socket)
return socket->state(); return socket->state();
SymbianUtils::OstChannel *ost = qobject_cast<SymbianUtils::OstChannel*>(d->device);
if (ost) {
//TODO we need some handshaking here
/*
if (ost->hasReceivedData())
return QAbstractSocket::ConnectedState;
else if (ost->isOpen())
return QAbstractSocket::ConnectingState;
*/
if (ost->isOpen()) return QAbstractSocket::ConnectedState;
}
return QAbstractSocket::UnconnectedState; return QAbstractSocket::UnconnectedState;
} }
@@ -317,12 +304,6 @@ void QmlDebugConnection::flush()
socket->flush(); socket->flush();
return; return;
} }
SymbianUtils::OstChannel *ost = qobject_cast<SymbianUtils::OstChannel*>(d->device);
if (ost) {
ost->flush();
return;
}
} }
void QmlDebugConnection::connectToHost(const QString &hostName, quint16 port) void QmlDebugConnection::connectToHost(const QString &hostName, quint16 port)
@@ -339,22 +320,6 @@ void QmlDebugConnection::connectToHost(const QString &hostName, quint16 port)
QIODevice::open(ReadWrite | Unbuffered); QIODevice::open(ReadWrite | Unbuffered);
} }
void QmlDebugConnection::connectToOst(const QString &port)
{
SymbianUtils::OstChannel *ost = SymbianUtils::SymbianDeviceManager::instance()->getOstChannel(port, KQmlOstProtocolId);
if (ost) {
ost->setParent(d);
d->device = ost;
d->connectDeviceSignals();
d->gotHello = false;
QIODevice::open(ReadWrite | Unbuffered);
emit stateChanged(QAbstractSocket::ConnectedState);
emit connected();
} else {
emit error(QAbstractSocket::HostNotFoundError);
}
}
void QmlDebugConnectionPrivate::connectDeviceSignals() void QmlDebugConnectionPrivate::connectDeviceSignals()
{ {
connect(device, SIGNAL(bytesWritten(qint64)), q, SIGNAL(bytesWritten(qint64))); connect(device, SIGNAL(bytesWritten(qint64)), q, SIGNAL(bytesWritten(qint64)));

View File

@@ -45,7 +45,6 @@ public:
~QmlDebugConnection(); ~QmlDebugConnection();
void connectToHost(const QString &hostName, quint16 port); void connectToHost(const QString &hostName, quint16 port);
void connectToOst(const QString &port);
qint64 bytesAvailable() const; qint64 bytesAvailable() const;
bool isConnected() const; bool isConnected() const;

View File

@@ -233,12 +233,7 @@ QUrl QDeclarativeFolderListModel::parentFolder() const
QString localFile = d->folder.toLocalFile(); QString localFile = d->folder.toLocalFile();
if (!localFile.isEmpty()) { if (!localFile.isEmpty()) {
QDir dir(localFile); QDir dir(localFile);
#if defined(Q_OS_SYMBIAN) || defined(Q_OS_WIN) dir.cdUp();
if (dir.isRoot())
dir.setPath("");
else
#endif
dir.cdUp();
localFile = dir.path(); localFile = dir.path();
} else { } else {
int pos = d->folder.path().lastIndexOf(QLatin1Char('/')); int pos = d->folder.path().lastIndexOf(QLatin1Char('/'));

View File

@@ -1,2 +0,0 @@
INCLUDEPATH *= $$PWD/../../shared/symbianutils $$PWD/../../shared/json
LIBS *= -l$$qtLibraryName(symbianutils)

View File

@@ -1,5 +0,0 @@
TEMPLATE = lib
TARGET = symbianutils
DEFINES += SYMBIANUTILS_BUILD_LIB JSON_BUILD_LIB
include(../../qtcreatorlibrary.pri)
include(../../shared/symbianutils/symbianutils.pri)

View File

@@ -1,69 +0,0 @@
import qbs.base 1.0
import "../QtcLibrary.qbs" as QtcLibrary
QtcLibrary {
name: "symbianutils"
cpp.includePaths: [
".",
"..",
"../../shared/symbianutils",
"../../shared/json"
]
cpp.defines: [
"SYMBIANUTILS_BUILD_LIB",
"JSON_BUILD_LIB",
"JSON_INCLUDE_PRI",
"JSON_BUILD_LIB",
"HAS_SERIALPORT"
]
cpp.optimization: "fast"
Depends { name: "cpp" }
Depends { name: "Qt.network" }
Depends { name: "Utils" }
Group {
condition: qbs.targetOS == "linux" || qbs.targetOS == "mac"
files: [
"../../shared/symbianutils/virtualserialdevice_posix.cpp"
]
}
Group {
condition: qbs.targetOS == "windows"
files: [
"../../shared/symbianutils/virtualserialdevice_win.cpp"
]
}
files: [
"../../shared/symbianutils/callback.h",
"../../shared/symbianutils/codadevice.cpp",
"../../shared/symbianutils/codadevice.h",
"../../shared/symbianutils/codamessage.cpp",
"../../shared/symbianutils/codamessage.h",
"../../shared/symbianutils/codautils.cpp",
"../../shared/symbianutils/codautils.h",
"../../shared/symbianutils/codautils_p.h",
"../../shared/symbianutils/symbiandevicemanager.cpp",
"../../shared/symbianutils/symbiandevicemanager.h",
"../../shared/symbianutils/symbianutils_global.h",
"../../shared/symbianutils/virtualserialdevice.cpp",
"../../shared/symbianutils/virtualserialdevice.h",
"../../shared/json/json_global.h",
"../../shared/json/json.h",
"../../shared/json/json.cpp"
]
ProductModule {
Depends { name: "cpp" }
cpp.includePaths: [
"../../shared/symbianutils",
"../../shared/json",
"."
]
cpp.defines: "JSON_INCLUDE_PRI"
}
}

View File

@@ -50,7 +50,6 @@ namespace Utils {
E.g. following file paths: E.g. following file paths:
\list \list
\i C:/app-build-desktop/qml/app/main.qml (shadow build directory) \i C:/app-build-desktop/qml/app/main.qml (shadow build directory)
\i C:/Private/e3026d63/qml/app/main.qml (Application data folder on Symbian device)
\i /Users/x/app-build-desktop/App.app/Contents/Resources/qml/App/main.qml (folder on Mac OS X) \i /Users/x/app-build-desktop/App.app/Contents/Resources/qml/App/main.qml (folder on Mac OS X)
\endlist \endlist

View File

@@ -7,8 +7,8 @@ DebuggerManager who is responsible for "doing the work".
The DebuggerManager creates all DebuggerEngines, and has zero or one The DebuggerManager creates all DebuggerEngines, and has zero or one
"current" Engine. Engines represent an interface to a "native" debugger. "current" Engine. Engines represent an interface to a "native" debugger.
Right now there are engines for gdb (used for C++ on Linux, Mac, Windows/MinGW, Right now there are engines for gdb (used for C++ on Linux, Mac, Windows/MinGW
Maemo and Symbian), for cdb (used for C++ on Windows/MSVC) and "script" (used and Maemo), for cdb (used for C++ on Windows/MSVC) and "script" (used
for JavaScript on all platforms). for JavaScript on all platforms).
The GdbEngine has different "Adapters" to cope with the variety of environments The GdbEngine has different "Adapters" to cope with the variety of environments
@@ -28,13 +28,9 @@ for JavaScript on all platforms).
RemoteGdbAdapter is used to talk to gdbserver running on Linux. RemoteGdbAdapter is used to talk to gdbserver running on Linux.
TrkGdbAdapter is used to talk to Symbian devices using the gdb protocol and
the gdb serial protocol between gdb and the Adapter and the TRK protocol
between the adapter and AppTRK running on the device.
Gdb comes in main two flavours: with or without Python. The Python version Gdb comes in main two flavours: with or without Python. The Python version
is preferred, but it is not available on Mac and on older versions of Linux. is preferred, but it is not available on Mac and on older versions of Linux.
On Windows, Symbian and Maemo we only support the Python version. On Windows and Maemo we only support the Python version.
The non-Python versions use the compiled version of the debugging helpers, The non-Python versions use the compiled version of the debugging helpers,
that needs to be enabled in the Qt4 Versions dialog, the Python version use that needs to be enabled in the Qt4 Versions dialog, the Python version use
@@ -50,24 +46,24 @@ for JavaScript on all platforms).
Per platform the situation for C++ debugging looks like: Per platform the situation for C++ debugging looks like:
[Helper loading strategy: /i - injected, /p - preload, /- not available] [Helper loading strategy: /i - injected, /p - preload, /- not available]
Symbian Maemo Linux Mac Windows Maemo Linux Mac Windows
MinGW MSVC MinGW MSVC
Engine: gdb gdb gdb gdb gdb cdb Engine: gdb gdb gdb gdb cdb
Python: yes yes yes no no no (not/appl) Python: yes yes no no no (not/appl)
Adapters: trk remote term term/i term/i term term/i Adapters: remote term term/i term/i term term/i
plain plain/p plain/i plain plain/i plain plain/p plain/i plain plain/i
attach attach/i attach/i attach attach/i attach attach/i attach/i attach attach/i
remote attach/- remote/- remote remote attach/- remote/- remote
Minimum Minimum
supported FSF FSF FSF FSF Apple FSF - supported FSF FSF FSF Apple FSF -
version: 7.1 7.1 7.1 6.8 1344 7.2 version: 7.1 7.1 6.8 1344 7.2
(no python) (no python)
Version FSF FSF FSF (XCode) FSF - Version FSF FSF (XCode) FSF -
in SDK: 7.2 7.1 7.2 7.2 in SDK: 7.1 7.2 7.2
(no python) (no python)

Some files were not shown because too many files have changed in this diff Show More