Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Building Qt for Symbian 3 Devices: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Building Qt for Symbian^3 devices= | [[Category:Developing_Qt::Symbian]]<br />[toc align_right="yes&quot; depth="3&quot;] | ||
= Building Qt for Symbian^3 devices = | |||
This guide provides information required to set up environment and build Qt libraries that can be installed on a Symbian^3 device. The produced libraries will not be binary compatible with any official Qt releases, so any applications you wish to run must be also built against these libraries. | This guide provides information required to set up environment and build Qt libraries that can be installed on a Symbian^3 device. The produced libraries will not be binary compatible with any official Qt releases, so any applications you wish to run must be also built against these libraries. | ||
==Environment setup== | == Environment setup == | ||
===The following tools are needed for building a Qt package:=== | === The following tools are needed for building a Qt package: === | ||
* | * "ActiveState Perl 5.6.1 (build 638) or newer&quot;:http://www.symlab.org/wiki/index.php/Kits_Q&amp;As#How_do_I_install_Perl_on_my_C.2B.2B_development_PC.3F - Required by Qt and Symbian toolchains. | ||
* | * "ActiveState Python 2.6.x or newer&quot;:http://www.symlab.org/wiki/index.php/Kits_Q&amp;As#How_do_I_install_Python_on_my_C.2B.2B_development_PC.3F - Required by Symbian toolchain. | ||
* | * "PDT 1.7 or newer&quot;:http://www.symlab.org/wiki/index.php/Product_Development_Toolkit_Quick_Start - Needed for Raptor (sbsv2) toolchain. Also includes Carbide IDE and other assorted tools. | ||
* | * "PDK 3.0.3 or newer&quot;:http://www.symlab.org/wiki/index.php/How_to_Download_a_PDK - Symbian platform. | ||
** Note: Installing some parts of the | ** Note: Installing some parts of the PDK require "SYMBIAN FOUNDATION RESEARCH & DEVELOPMENT LICENSE&quot;, but those parts are not needed to build Qt so you don't need to worry about missing them. | ||
* The recommended compiler for building Qt libraries is | * The recommended compiler for building Qt libraries is "RVCT 2.2 (build 686 or newer)":http://www.symlab.org/wiki/index.php/ARM_Real_View_Compilation_Tools_(RVCT)''Quick_Start - which is not available free of charge.<br />'''''' Alternatively, "RVCT 4.0 (build 821 or newer)":http://www.symlab.org/wiki/index.php/ARM_Real_View_Compilation_Tools''(RVCT)_Quick_Start can be used. Unlike version 2.2, version 4.0 is available free of charge for small organizations. | ||
* The desired version of Qt source code - Available e.g. via "Gitorius&quot;:http://qt.gitorious.org/+qt-developers/qt/releases or "ftp&quot;:ftp://ftp.qt.nokia.com/qt/source/ (e.g. qt-everywhere-opensource-src-4.7.1.zip). | |||
* The desired version of Qt source code | |||
===Required environment variables:=== | === Required environment variables: === | ||
* | * EPOCROOT environment variable must point to PDK root. E.g. <code&gt;set EPOCROOT=C:PDK3.0.3</code&gt; | ||
* Depending on compiler you are using: | * Depending on compiler you are using: | ||
** RVCT22BIN, RVCT22INC, and RVCT22LIB. These need to point to | ** RVCT22BIN, RVCT22INC, and RVCT22LIB. These need to point to <code&gt;bin&lt;/code&gt;, <code&gt;inc&lt;/code&gt; (or <code&gt;include&lt;/code&gt;), and <code&gt;lib&lt;/code&gt; directories under your RVCT 2.2 installation. Normally these are set by RVCT 2.2 installer. | ||
** RVCT40BIN, RVCT40INC, and RVCT40LIB are the corresponding variables for | ** RVCT40BIN, RVCT40INC, and RVCT40LIB are the corresponding variables for RVCT 4.0. | ||
* | * PATH environment variable must contain the following paths in the beginning to ensure correct tools are used. | ||
** | ** <code&gt;lt;Qt source rootgt;bin&lt;/code&gt; for qmake and Qt tools. | ||
** | ** <code&gt;lt;PDT installation rootgt;Raptorwin32mingwbin&lt;/code&gt; for Mingw make. | ||
** | ** <code&gt;lt;PDT installation rootgt;Raptorbin&lt;/code&gt; for sbs tool. | ||
** | ** <code&gt;EPOCROOT%epoc32tools&lt;/code&gt; for required Symbian tools. | ||
<br />Here are sample commands you can edit to match your environment and save as ''setenv.bat'' to set up your Qt building environment: | |||
<br />Change to your Qt source root directory:<br /><code> C:<br /> cd </code> | |||
<br />Set up the environment variables: | |||
<br /><code> SET EPOCROOT=C:.0.3 SET RVCT22BIN=C:_22\bin<br /> SET RVCT22INC=C:_22\inc<br /> SET RVCT22LIB=C:_22\lib<br /> SET PATH=&#x25;CD&amp;#x25;;C:_1.7\Raptor\win32\mingw\bin;C:_1.7\Raptor\bin;&#x25;EPOCROOT&amp;#x25;epoc32\tools;&#x25;PATH&amp;#x25; | |||
<br /></code> | |||
<br />h3. Signing certificate | |||
<br />A signing certificate is needed if you are not satisfied with the default self-signable set of supported capabilities for Qt libraries (i.e. LocalServices, NetworkServices, ReadUserData, UserEnvironment, and WriteUserData). The capabilities Qt libraries require depends on the capabilities of the applications you plan on running against the Qt libraries you build; the Qt libraries need at least all of the capabilities the application has. The best certificate to use would be a manufacturer’s RnD certificate, but unless you are working for a device manufacturer, you probably won’t have access to such a certificate. The next best thing is a Symbian developer certificate. See "here&quot;:https://www.symbiansigned.com/app/page for details about acquiring a developer certificate. | |||
<br />h2. Building Qt | |||
<br />h3. Configure Qt | |||
<br />Give the following command in your Qt source root directory to configure Qt: | |||
<br /><code>configure -platform win32-g++ -xplatform symbian-sbsv2 -openvg -graphicssystem openvg -no-usedeffiles -nomake demos -nomake examples -qtlibinfix OfMyOwn -make make<br /></code> | |||
<br />* '''Note:''' If you do not need Webkit, you can reduce the build time around 50 by adding “-no-webkit” parameter to configure. | |||
=== | === Build Qt & QtWebkit === | ||
Depending on your chosen compiler, select one of commands below to compile Qt and give it at the Qt source root directory: | |||
<code>make release-armv6<br />make release-armv6-rvct4.0<br /></code> | |||
== | == Installing Qt libraries to device == | ||
By default Qt libraries are built with “All -Tcb” capabilities, which requires a certificate normally only available for device manufacturers to sign. Depending on what kind of certificate you have available, you might need to patch the capabilities of the Qt libraries. To create Qt installation packages, run the following commands: | |||
If you are content with default set of self-signable capabilities and do not have any extra certificate: | |||
= | <code>cd src\s60installs<br />make sis QT_SIS_OPTIONS=-i | ||
cd ..rdparty\webkit\WebCore<br />make sis QT_SIS_OPTIONS=-i<br /></code> | |||
== | If you have a manufacturer RnD certificate and a RnD device:<br /><code><br />cd src\s60installs<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt; | ||
cd ..rdparty\webkit\WebCore<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt;<br /></code> | |||
If you are | If you are using developer certificate with maximum non-manufacturer capabilities: | ||
<code>cd src\s60installs<br />patch_capabilities.pl QtOfMyOwn_template.pkg release-armv6 "ALL -Tcb -AllFiles -DRM&quot;<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt; | |||
cd ..rdparty\webkit\WebCore<br />patch_capabilities.pl QtWebKitOfMyOwn_template.pkg release-armv6 "ALL -Tcb -AllFiles -DRM&quot;<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt;<br /></code> | |||
* '''Note 1:''' | * '''Note 1:''' <code&gt;QT_SIS_OPTIONS=-i&lt;/code&gt; is simply a convenience parameter that causes automatic installation to a connected device after package is created. | ||
* '''Note 2:''' Infixing Qml plugins is broken in Qt 4.7.0 and 4.7.1 releases, so if the device already has Qt 4.7.x pre-installed, you will need to edit the .pkg files and remove all lines with qmldir on them before creating the package or you won’t be able to install it due to same files already having been installed by existing package. You can also expect qml plugins not working properly with infixed Qt in these releases. | * '''Note 2:''' Infixing Qml plugins is broken in Qt 4.7.0 and 4.7.1 releases, so if the device already has Qt 4.7.x pre-installed, you will need to edit the .pkg files and remove all lines with qmldir on them before creating the package or you won’t be able to install it due to same files already having been installed by existing package. You can also expect qml plugins not working properly with infixed Qt in these releases. | ||
==Building applications== | == Building applications == | ||
Build your own applications normally using the same make target that you used to build the Qt and use same “make sis” options. E.g. for RVCT 2.2 build using self-signed certificate, use the following commands: | |||
<code>cd <your app dir&gt;<br />qmake<br />make release-armv6<br />make sis QT_SIS_OPTIONS=-i<br /></code> | |||
Revision as of 10:06, 24 February 2015
[toc align_right="yes" depth="3"]
Building Qt for Symbian^3 devices
This guide provides information required to set up environment and build Qt libraries that can be installed on a Symbian^3 device. The produced libraries will not be binary compatible with any official Qt releases, so any applications you wish to run must be also built against these libraries.
Environment setup
The following tools are needed for building a Qt package:
- "ActiveState Perl 5.6.1 (build 638) or newer":http://www.symlab.org/wiki/index.php/Kits_Q&As#How_do_I_install_Perl_on_my_C.2B.2B_development_PC.3F - Required by Qt and Symbian toolchains.
- "ActiveState Python 2.6.x or newer":http://www.symlab.org/wiki/index.php/Kits_Q&As#How_do_I_install_Python_on_my_C.2B.2B_development_PC.3F - Required by Symbian toolchain.
- "PDT 1.7 or newer":http://www.symlab.org/wiki/index.php/Product_Development_Toolkit_Quick_Start - Needed for Raptor (sbsv2) toolchain. Also includes Carbide IDE and other assorted tools.
- "PDK 3.0.3 or newer":http://www.symlab.org/wiki/index.php/How_to_Download_a_PDK - Symbian platform.
- Note: Installing some parts of the PDK require "SYMBIAN FOUNDATION RESEARCH & DEVELOPMENT LICENSE", but those parts are not needed to build Qt so you don't need to worry about missing them.
- The recommended compiler for building Qt libraries is "RVCT 2.2 (build 686 or newer)":http://www.symlab.org/wiki/index.php/ARM_Real_View_Compilation_Tools_(RVCT)Quick_Start - which is not available free of charge.
' Alternatively, "RVCT 4.0 (build 821 or newer)":http://www.symlab.org/wiki/index.php/ARM_Real_View_Compilation_Tools(RVCT)_Quick_Start can be used. Unlike version 2.2, version 4.0 is available free of charge for small organizations. - The desired version of Qt source code - Available e.g. via "Gitorius":http://qt.gitorious.org/+qt-developers/qt/releases or "ftp":ftp://ftp.qt.nokia.com/qt/source/ (e.g. qt-everywhere-opensource-src-4.7.1.zip).
Required environment variables:
- EPOCROOT environment variable must point to PDK root. E.g. <code>set EPOCROOT=C:PDK3.0.3</code>
- Depending on compiler you are using:
- RVCT22BIN, RVCT22INC, and RVCT22LIB. These need to point to <code>bin</code>, <code>inc</code> (or <code>include</code>), and <code>lib</code> directories under your RVCT 2.2 installation. Normally these are set by RVCT 2.2 installer.
- RVCT40BIN, RVCT40INC, and RVCT40LIB are the corresponding variables for RVCT 4.0.
- PATH environment variable must contain the following paths in the beginning to ensure correct tools are used.
- <code>lt;Qt source rootgt;bin</code> for qmake and Qt tools.
- <code>lt;PDT installation rootgt;Raptorwin32mingwbin</code> for Mingw make.
- <code>lt;PDT installation rootgt;Raptorbin</code> for sbs tool.
- <code>EPOCROOT%epoc32tools</code> for required Symbian tools.
Here are sample commands you can edit to match your environment and save as setenv.bat to set up your Qt building environment:
Change to your Qt source root directory:
C:<br /> cd
Set up the environment variables:
SET EPOCROOT=C:.0.3 SET RVCT22BIN=C:_22\bin<br /> SET RVCT22INC=C:_22\inc<br /> SET RVCT22LIB=C:_22\lib<br /> SET PATH=&#x25;CD&amp;#x25;;C:_1.7\Raptor\win32\mingw\bin;C:_1.7\Raptor\bin;&#x25;EPOCROOT&amp;#x25;epoc32\tools;&#x25;PATH&amp;#x25;
<br />
h3. Signing certificate
A signing certificate is needed if you are not satisfied with the default self-signable set of supported capabilities for Qt libraries (i.e. LocalServices, NetworkServices, ReadUserData, UserEnvironment, and WriteUserData). The capabilities Qt libraries require depends on the capabilities of the applications you plan on running against the Qt libraries you build; the Qt libraries need at least all of the capabilities the application has. The best certificate to use would be a manufacturer’s RnD certificate, but unless you are working for a device manufacturer, you probably won’t have access to such a certificate. The next best thing is a Symbian developer certificate. See "here":https://www.symbiansigned.com/app/page for details about acquiring a developer certificate.
h2. Building Qt
h3. Configure Qt
Give the following command in your Qt source root directory to configure Qt:
configure -platform win32-g++ -xplatform symbian-sbsv2 -openvg -graphicssystem openvg -no-usedeffiles -nomake demos -nomake examples -qtlibinfix OfMyOwn -make make<br />
* Note: If you do not need Webkit, you can reduce the build time around 50 by adding “-no-webkit” parameter to configure.
Build Qt & QtWebkit
Depending on your chosen compiler, select one of commands below to compile Qt and give it at the Qt source root directory:
make release-armv6<br />make release-armv6-rvct4.0<br />
Installing Qt libraries to device
By default Qt libraries are built with “All -Tcb” capabilities, which requires a certificate normally only available for device manufacturers to sign. Depending on what kind of certificate you have available, you might need to patch the capabilities of the Qt libraries. To create Qt installation packages, run the following commands:
If you are content with default set of self-signable capabilities and do not have any extra certificate:
cd src\s60installs<br />make sis QT_SIS_OPTIONS=-i
cd ..rdparty\webkit\WebCore<br />make sis QT_SIS_OPTIONS=-i<br />
If you have a manufacturer RnD certificate and a RnD device:
<br />cd src\s60installs<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt;
cd ..rdparty\webkit\WebCore<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt;<br />
If you are using developer certificate with maximum non-manufacturer capabilities:
cd src\s60installs<br />patch_capabilities.pl QtOfMyOwn_template.pkg release-armv6 "ALL -Tcb -AllFiles -DRM&quot;<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt;
cd ..rdparty\webkit\WebCore<br />patch_capabilities.pl QtWebKitOfMyOwn_template.pkg release-armv6 "ALL -Tcb -AllFiles -DRM&quot;<br />make sis QT_SIS_OPTIONS=-i QT_SIS_CERTIFICATE=<certificate file&gt; QT_SIS_KEY=<certificate key file&gt;<br />
- Note 1: <code>QT_SIS_OPTIONS=-i</code> is simply a convenience parameter that causes automatic installation to a connected device after package is created.
- Note 2: Infixing Qml plugins is broken in Qt 4.7.0 and 4.7.1 releases, so if the device already has Qt 4.7.x pre-installed, you will need to edit the .pkg files and remove all lines with qmldir on them before creating the package or you won’t be able to install it due to same files already having been installed by existing package. You can also expect qml plugins not working properly with infixed Qt in these releases.
Building applications
Build your own applications normally using the same make target that you used to build the Qt and use same “make sis” options. E.g. for RVCT 2.2 build using self-signed certificate, use the following commands:
cd <your app dir&gt;<br />qmake<br />make release-armv6<br />make sis QT_SIS_OPTIONS=-i<br />