Quickstart Example |
Domain | Value |
---|---|
Bearer Management | bearer |
Contacts | contacts |
Location | location |
Multimedia | multimedia |
Messaging | messaging |
Publish And Subscribe | publishsubscribe |
Service Framework | serviceframework |
Sensor API | sensors |
System Information | systeminfo |
Versit | versit |
When developing on Symbian we will also need to add the required capabilites to the project file in order to satisfy the Symbian security model. This can be achieved with a line such as the following:
TARGET.CAPABILITY = CAPABILITY_A CABAPILITY_B
CAPABILITY_A and CAPABILITY_B are place holders for the appropriate Symbian capabilities. A complete list of all Symbian capabilities and their availability to application developers can be found in the Symbian capability documentation.
The subsequent table provides an overview of possibily required capabilities for each Mobility library. Note that not all capabilities are always required when using a particular API. The exact list depends on which parts of an API is utilized by an application.
Domain | Symbian Capabilities |
---|---|
Bearer Management | ReadUserData NetworkServices (NetworkControl for QNetworkSession::stop()) |
Contacts | ReadUserData WriteUserData |
Location | Location |
Multimedia | UserEnvironment ReadUserData WriteUserData ReadDeviceData WriteDeviceData |
Messaging | LocalServices ReadUserData WriteUserData NetworkServices UserEnvironment ReadDeviceData WriteDeviceData |
Publish And Subscribe | Capability depends on P&S value being read/written. API itself doesn't require any capability. |
Service Framework | No capabilities requried by itself, the plugins may have capability requirements. |
Sensor API | ReadDeviceData |
System Information | LocalServices ReadUserData WriteUserData NetworkServices UserEnvironment Location ReadDeviceData |
Versit API | No additional capabilities required. |
The complete list of all Symbian capabilities and how they can be obtained can be found in the Symbian developer documentation.
And we're done. If you are using the command line simply enter:
qmake
make //or nmake on Windows
to generate the executable which can then be run.
If you are developing for Symbian, to make a debug build for the emulator run:
qmake make debug-winscw
This assumes that qmake is in your %PATH% and Qt has been built for the emulator already.
To make a release build and SIS package for a device run:
qmake make release-gcce make sis
For further details on how to build applications for Symbian see The Symbian Platform - Introduction to Qt and Qt Quick Start
Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. | Qt qtmobility-1.0 | |
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD. | ||
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP ! |
Copyright © 2000-2012 - www.developpez.com