Building Qt 4 for BlackBerry

Building Qt4 for BlackBerry

This page provides instructions on how to build Q4 for BlackBerry10 and PlayBook OS. These instructions are addressed to those who need to build a custom version of Qt for their application to work on BlackBerry10 products, or would like to develop applications for PlaybookOS . Developers looking to create applications which do not have unusual needs should rather use QtCreator 3.0 and Qt provided in the BlackBerry 10 NDK, see [[Qt-Creator-with-BlackBerry-10] | this page]] for more details.

Setting up the environment

See Blackberry for the introduction and further instructions.

Open a terminal window and load the Blackberry NDK enviroment variables with:

source /opt/bbndk-2.1.0/bbndk-env.sh <code>

All the commands below should be ran in the same terminal window.<br />If you close it between steps ''you need to run the bbndk-env.sh again''.

=== Getting the source ===

git clone git://gitorious.org/qt/qt.git

NOTE: we suggest to start with a clean source tree before building for different architectures (ARM/x86).

On the Playbook, the last officially supported version is 4.8.3. The recommended version is 4.8.3. To switch to 4.8.3, do:

<br /> cd qt<br /> git checkout v4.8.3<br />

Those who would like to use a more recent version of Qt 4.8 for the Playbook will need to use the blackberry-playbook-armv7le-qcc mkspec instead of the usual blackberry-armv7le-qcc. Please be advised that versions later than 4.8.3 are not officially supported and are not guaranteed to work. Use it at your own risk.

Building on a Linux/OS X host.

Building Qt 4.8 for ARM (BlackBerry 10 and PlaybookOS)

<br /> cd qt<br /> ./configure -opensource -confirm-license -qpa -iconv -shared -release -xplatform blackberry-armv7le-qcc <br /> -little-endian -arch arm -largefile -nomake examples -xmlpatterns -no-webkit -no-rpath  -opengl es2 -reduce-exports -system-sqlite -prefix &lt;prefix&amp;gt;<br /> make<br /> make install<br />

When compiling for the Playbook, you also need the -no-neon option, as NEON support on the Playbook is known to be flaky. This is only required for Qt 4.8.3 or later.

Building Qt 4.8 for x86 (Simulator)

<br /> cd qt<br /> ./configure -opensource -confirm-license -qpa -iconv -shared -release -xplatform blackberry-x86-qcc <br /> -little-endian -arch i386 -largefile -nomake examples -nomake demos -xmlpatterns -no-webkit  -no-rpath -opengl es2 -reduce-exports -system-sqlite -prefix &lt;prefix&amp;gt;<br /> make<br /> make install<br />

Qt will be installed at $PWD/stage. Alternatively, you can then use -prefix-install and pass a directory to the -prefix option to change the installation directory.

<br /> ./configure -opensource -confirm-license -qpa -iconv -shared -release -xplatform blackberry-x86-qcc <br /> -little-endian -arch i386 -largefile -nomake examples* -nomake demos -xmlpatterns -no-webkit  -no-rpath -opengl es2 -reduce-exports -system-sqlite* -prefix-install -prefix ~/build/<br />

Building on a Windows host

In order to build Qt 4.8 for BlackBerry on a Windows host, you will need to rebuild the <code&gt;configure.exe&lt;/code&gt; utility first:
# Clone <code&gt;git://gitorious.org/qt/qt.git&lt;/code&gt; to a separated directory;

For Playbook users only: You need to checkout tag v4.8.3 and cherry-pick c14694621aab2e7df13830f80621fb5680b432e4 before you can continue.

1. Configure Qt with <code&gt;configure.exe -opensource -confirm-license&lt;/code&gt;
2. <code&gt;cd&lt;/code&gt; into <code&gt;tools/configure&lt;/code&gt;
3. Rebuild with <code&gt;..</code&gt; and then <code&gt;mingw32-make&lt;/code&gt;
4. The new <code&gt;configure.exe&lt;/code&gt; binary will be place on <code&gt;$QTSRC/configure.exe&lt;/code&gt;
5. You can now use it to replace the <code&gt;configure.exe&lt;/code&gt; on the Qt source tree you will use to build for BlackBerry.

Building Qt 4.8 for ARM (Playbook and phone devices)

<br />C:&gt; cd qt<br />C:&gt;configure.exe -opensource -confirm-license -release -xplatform blackberry-armv7le-qcc -arch arm -nomake examples -nomake demos -no-webkit -opengl es2 -inotify -prefix c:stall<br />C:&gt; mingw32-make -j<br />C:&gt; mingw32-make -j install<br />

When compiling for the Playbook, also supply the -no-neon option (see above for the reasons).

Building Qt 4.8 for x86 (Simulator)

<br />C:&gt; cd qt<br />C:&gt; configure.exe -opensource -confirm-license -release -xplatform blackberry-x86-qcc -arch i386 -nomake examples -nomake demos -no-webkit -opengl es2 -inotify -prefix c:stall<br />C:&gt; mingw32-make -j<br />C:&gt; mingw32-make -j install<br />

Qt will be installed at C:stall. Alternatively, you can then use <code&gt;-prefix-install&lt;/code&gt; and pass a directory to the <code&gt;-prefix&lt;/code&gt; option to change the installation directory.

Building QtMobility

"QtMobility&quot;:http://doc.trolltech.com/qtmobility-1.2/ is an addon module to Qt that provides various modules for mobile device functions. For BlackBerry devices, the sensor and multimedia backends are implemented, providing access to the device's sensors such as the accelerometer or the light sensor, and providing the ability to playback audio and video.
For various reasons, such as that there will be no more official releases of QtMobility for Qt4, the repository of QtMobility is a "fork&quot;:https://gitorious.org/+kdab-developers/qt-mobility/qnx-qt-mobility of the upstream one (unlike the Qt5 version, in which the BlackBerry backends are all upstream).

Building on a Linux host

To build QtMobility on a Linux host, first make sure that the qmake of the cross-compiled Qt from above is first in $PATH. $QTDIR needs to be set to the path of the Qt installation from above. Otherwise, the environment should be the same as when Qt itself was built.

<br />$ git clone git://gitorious.org/+kdab-developers/qt-mobility/qnx-qt-mobility.git<br />$ cd qnx-qt-mobility<br />$ ./configure -prefix $QTDIR<br />$ make<br />$ make install<br />

Now QtMobility is installed into the Qt installation and is ready to be used.

See also

• Building Qt5 for Blackberry
• A HelloWorld using the Blackberry NDK CLI tools
• Building_and_Deploying_Qt_Applications_to_the_Playbook