              
The Symbian platform - Introduction to QtRequired ToolsSee Qt for the Symbian platform Requirements to see what tools are required to use Qt for the Symbian platform. Installing Qt and Running DemosFollow the instructions found in Installing Qt for the Symbian platform to learn how to install Qt using using source package and how to build and run the Qt demos. Building Your Own ApplicationsIf you are new to Qt development, have a look at How to Learn Qt. In general, the difference between developing a Qt application on the Symbian platform compared to any of the other platforms supported by Qt is not that big. Once you have created a .pro file for your project, generate the Symbian specific Bld.inf and .mmp files this way: qmake For more information on how to use qmake have a look at the qmake Tutorial. In particular, see the qmake Platform Notes for details of Symbian-specific build settings. Now you can build the Qt for the Symbian platform application with standard build tools. Alternative Build TargetsBy default, running make will produce binaries for the emulator. However, the Symbian platform comes with several alternative build targets that can be used to create binaries for target hardware and deploy them on devices, as shown in the table below:
The following lines perform a debug build for the emulator and deploy all the needed files: make debug-winscw To work on your project in Carbide, simply import the .pro file by right clicking on the project explorer and executing "Import...". Running Applications from the Command LineThe application can be launched on the emulator using make run command. The application can be launched on a device using make runonphone command. When this command is invoked, a .sis file is first created as if make sis command was invoked (see above for details). Note: Running the application on a device using this command requires TRK application to be running on the device. Additional environment variables that can be utilized with these commands are:
Installing Your Own ApplicationsTo install your own applications on hardware, you need a signed .sis file. (Refer to the Symbian Platform Security article for more informations about self-signing.) The signed .sis file can be created with make sis target. sis target is only supported for executables or projects with DEPLOYMENT statements. By default the sis target will create signed .sis file for last build target. For example, the following sequence will generate the needed makefiles, build the project for debug-winscw and release-armv5, and create self-signed .sis file for release-armv5 target: qmake
make debug-winscw release-armv5
make sis
If you want to use different certificate information or override the default target for .sis file creation you can use the environment variables as shown in the table below:
The supported options for QT_SIS_OPTIONS:
Execute the createpackage.pl script without any parameters for detailed information about options. By default no options are given. For example: set QT_SIS_TARGET=debug-armv5
make sis
The environment variables for make can also be given as parameters: make sis QT_SIS_TARGET=debug-armv5 If you want to install the program immediately after creating .sis file, make sure that the device is connected to the computer in "PC Suite" mode, and use deploy target instead of sis target: make deploy Deployment and the Smart InstallerAlthough some Symbian devices may already have a version of Qt installed on them, there needs to be a way to ensure that an appropriate version of Qt is available for your application to use. Rather than deploy the required Qt libraries with your application, the preferred way to package Qt applications for deployment is to download and use the Smart Installer. The Smart Installer makes sure that deployed applications have all the Qt dependencies they need to run on a device, performing the necessary updates when the user installs the application. More information about deployment can be found in the Deploying an Application on the Symbian Platform document. |
