Applications are deployed to Symbian devices in signed .sis package files. The .sis file content is controlled with .pkg files. The .pkg file contains a set of instructions used by tools to produce a .sis file. qmake generates a default .pkg file for your project. The .pkg file generated by qmake is typically fully functional for testing purposes but when planning to deliver your application to end-users some changes are needed. This document describes what changes are typically needed and how to implement them.
Download the latest release of the Smart Installer from http://get.qt.nokia.com/nokiasmartinstaller/, and install it on top of the Qt package.
Qt for the Symbian platform does not currently support static linking of Qt libraries with application binaries. You will need to build shared libraries as described below and link your application with them.
When deploying the application using the shared libraries approach we must ensure that the Qt runtime is correctly redistributed along with the application executable, and also that all Qt dependencies are redistributed along with the application.
We will demonstrate these procedures in terms of deploying the Wiggly application that is provided in Qt's examples directory.
We assume that you already have installed Qt as a shared library, in the C:\path\to\Qt directory which is the default when installing Qt for Symbian. For more information on how to build Qt, see the Installation documentation.
After ensuring that Qt is built as a shared library, we can build the Wiggly application. First, we must go into the directory that contains the application:
cd examples\widgets\wiggly
To prepare the application for deployment we must ensure that the .pkg file generated by qmake contains the relevant vendor information and embeds the necessary dependencies to the application deployment file (.sis). The content of the generated .pkg file can be controlled with the Symbian specific qmake DEPLOYMENT keyword extensions.
First, we will change the vendor statement to something more meaningful. The application vendor is visible to end-user during the installation.
vendorinfo = \
"%{\"Example Localized Vendor\"}" \
":\"Example Vendor\""
my_deployment.pkg_prerules = vendorinfo
DEPLOYMENT += my_deployment
Second we will tell the Symbian application installer that this application supports only S60 5.0 based devices:
supported_platforms = \
"; This demo only supports S60 5.0" \
"[0x1028315F],0,0,0,{\"S60ProductID\"}"
default_deployment.pkg_prerules -= pkg_platform_dependencies
my_deployment.pkg_prerules += supported_platforms
DEPLOYMENT += my_deployment
You can find a list of platform and device indentification codes from Forum Nokia Wiki. By default .pkg file generated by qmake adds support for all S60 3rd edition FP1, S60 3rd edition FP2 and S60 5th edition devices.
Now we are ready to compile the application and create the application deployment file. Run qmake to create Symbian specific makefiles, resources (.rss) and deployment packaging files (.pkg). And do build to create the application binaries and resources.
qmake make release-gcce
If everything compiled and linked without any errors, we are now ready to create an application installation package (wiggly_installer.sis).
If you haven't done so already, download the latest release of the Smart Installer from http://get.qt.nokia.com/nokiasmartinstaller/, and install it on top of the Qt package
Then use this command to create the installer sis package:
make installer_sis
If all binaries and dependencies were found, you should now have a self signed wiggly_installer.sis ready to be installed on a device. The smart installer contained in the in the installer package will download the necessary dependencies such as Qt libraries to the device.
Note: If you want to have your application properly Symbian Signed for distribution, you will have to properly sign both the application and the application installer packages. Please see Forum Nokia Wiki for more information about Symbian Signed.
For more information about creating a .sis file and installing it to device see also here.