Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Archived:Setting up environment for Qt Mobility API

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The Qt Mobility APIs are now present in the Qt SDK, which is the only SDK available for mobile development.

Article Metadata
Created: kiran10182 (08 Mar 2010)
Last edited: hamishwillee (21 Jun 2012)


This article explains how to set up a Symbian SDK to work with Qt Mobility APIs (this is no longer necessary because the APIs are included in the Qt SDK). Deprecated)



Setup Qt

  • Download Qt.
  • Install it on your PC.


  • Choose the path of installation

Qt4.6.2 choose path.PNG

  • Choose the Symbian SDK(s)

Qt4.6.2 choose SDK.PNG

  • Qt provides a command prompt configured with the correct paths and environment variables for building Qt applications from the command line:

Qt4.6.2 command prompt.PNG

Note.pngNote: Before testing a Qt application on a (S60 3rd Edition or 5th Edition) phone, Qt libraries must be installed on the device. Easiest way to do this is to connect the device to the PC using Nokia PC Suite and use the qt_installer.sis, located in the root folder of Qt installation. This .sis file will install all Qt libraries and dependencies to an S60 device.

Setup Qt Mobility API

  • After successful installation of Qt, the next step is to set up Qt Mobility
  • Download QtMobility API (also known as New Qt APIs) source and binary package for Symbian.
  • Edited by Rahul - I downloaded from here QTMobilitySymbian API above link was not having zip files required in next steps.
  • Extract the file to a suitable location. Here, C:\Qt is used.
  • Inside the package, you'll find the following files:
    • qtmobility.sis
  • Extract qt-mobility-1.0.0-epoc32-<S60 SDK>.zip packages into the root folder of the respective S60 SDK.
    • For example, if using S60 5th Edition SDK, extract into C:\S60\devices\S60_5th_Edition_SDK_v1.0. Repeat this step for all the Symbian SDKs you selected during Qt installation.

  • Extract into the root folder of each S60 SDK (as above).
    • This will enable Qt style include statements (e.g. #include <QSystemInfo> instead of #include <qsysteminfo.h>).

  • Install qtmobility.sis file to device. You can do this, for example, via bluetooth or using Nokia PC Suite (recommended).

  • Copy (and rename) C:/Qt/qt-mobility-symbian-opensource-1.0.0/features/mobility.prf.template file to <QTDIR>/mkspecs/features/mobility.prf
    • <QTDIR> can be obtained by running 'qmake -v' from the Qt command prompt.

You now have a working environment for building Qt projects that use QtMobility libraries.

Building the examples

To test that you have a working environment, try building the examples from Qt command prompt:

C:/Qt/qt-mobility-symbian-opensource-1.0.0> configure -examples

If configure completes successfully, build the examples:

C:/Qt/qt-mobility-symbian-opensource-1.0.0> cd examples
C:/Qt/qt-mobility-symbian-opensource-1.0.0/examples> qmake
C:/Qt/qt-mobility-symbian-opensource-1.0.0/examples> make release-gcce

To generate a sis package and automatically deploy it to a device connected to PC Suite, use createpackage command with -i option. For example:

C:/Qt/qt-mobility-symbian-opensource-1.0.0/examples> cd bearercloud
C:/Qt/qt-mobility-symbian-opensource-1.0.0/examples/bearercloud> createpackage -i bearercloud_template.pkg release-gcce

Note.pngNote: Using createpackage without certificate option will sign the application with a self-signed certificate. Only those examples that use basic capabilities (TARGET.CAPABILITY in .pro file), granted by the user during installation, can be self-signed. See Capabilities for more information.

Related articles

Reference links

This page was last modified on 21 June 2012, at 05:15.
73 page views in the last 30 days.