Home · All Classes · All Functions ·

Installation Guide

Get the Qt Mobility API Package

To begin, obtain the most recent distrubution package from http://get.qt.nokia.com

Pre-requisites & Dependencies

To install Qt Mobility you must already have installed Qt 4.6 or higher, visit http://get.qt.nokia.com to obtain a copy.

Qt Mobility Project APIs are comprised of a number of domains. Some of these domains have dependencies and these are outlined below:

APIDependencycompile timeruntime
MessagingThe linux backend depends on QMF. For more information on QMF visit QMF Labs article

The Windows Mobile backend depends on ActiveSync version 4.5.

While not supported for this release the Windows Desktop backend requires Microsoft Outlook 2003 or later, and Microsoft Windows XP to be installed.

The messaging API SMS/MMS functionality requires that the platform provides SMS/MMS facilites. Email functionality requires that an email account is available on the platform.

NY
ContactsThe Maemo 6 backend depends on libqttracker. For more information on libqttracker visit libqttracker public repository. Other components offered by the Maemo 6 platform may be required in order to support the full functionality of the Maemo 6 backend.YN
Service FrameworkThe Service Framework depends on SQLite version 3 and that Qt has been built with an sqlite driver. Building the driver by Qt is most easily achieved by using one of the following configure options: -qt-sql-sqlite, -plugin-sql-sqlite or -system-sqliteNY
MultimediaThe Multimedia component depends on the QtMultimedia module in Qt. Qt by default is configured to make this module with the -multimedia option.

The linux X11 backend requires that gstreamer be installed, including libgstreamer, gstreamer-devel, plugins-base and plugins-good packages. The linux backend was tested with gstreamer 0.10.19 and newer versions.

YN
LocationThe Symbian backend uses the LBT (Location Based Triggering) library for area notifications. Area notifications will be disabled at compile time if the LBT library is not found.

The LBT library is not publicly available at the time of writing. The developer documentation for S60 Location Services is probably the best source for LBT availability updates, as it will be updated when the library is relased.

N(Y)N
System InformationThe Linux backend depands on QtDBus, HAL and NetworkManager, although System Information will compile without them, there will be reduced functionality.

On Mac OS X, System Information depends on the 10.6 SDK (XCode 3.2.1), although it will compile with older SDK's there will be reduced functionality.

N(Y)N
Publish & SubscribeThe Maemo 6 backend depends on Context KitYN
Bearer ManagementThe Linux backend depends on QtDBus and NetworkManager, although Bearer Management will compile without them there will be reduced functionality.N(Y)N

Unpacking

Unpack the Qt Mobility archive if you have not done so already, on Unix (X11 and Mac):

    cd /tmp
    gunzip %DISTNAME%.tar.gz        #uncompress the archive
    tar xvf %DISTNAME%.tar          #unpack it

This creates the directory /tmp/%DISTNAME% containing the files from the archive. We only support the GNU version of the tar archiving utility. Note on some systems it is called gtar.

On windows, uncompress the zip file into the directory you want Qt Mobility Project installed, extracting to C:\QtMobility will create the directory C:\QtMobility\%DISTNAME%

NOTE: The install path must not contain any spaces.

Building

Ensure that all compile time dependencies for your particular platform have been met before building.

Building On Unix

To configure the Qt Mobility libraries for your machine, run the ./configure script in the package directory.

To specify the installation directory you may use the -prefix option. Not passing a prefix installs the mobility libraries into $PWD/install.

    cd /tmp/%DISTNAME%
    ./configure -prefix $TARGET_DIR

Type ./configure -help to get a list of all available options. If you are building for maemo you need to use the -maemo option with configure.

To create all the libraries and tools, type:

    make

To install the libraries and tools to $TARGET_DIR, type:

    make install

If you have specified an install directory with root ownership, you will need to type:

    su -c "make install"
        or
    sudo make install

and enter in the appropriate password.

Note that on some systems the make utility is named differently, e.g. gmake. The configure script tells you which make utility to use.

Building On Windows

To configure the Qt Mobility libraries for your machine, run configure in the package directory.

To specify the installation directory you may use the -prefix option. Not passing a prefix installs the mobility libraries into an install directory within the current working directory.

        cd c:\QtMobility\%DISTNAME%
        configure -prefix %TARGET_DIR%

Type configure -help to get a list of all available options.

The actual commands needed to build and install Qt Mobility depends on your development system. For Microsoft Visual Studio to create and install the libraries and tools type:

    nmake
    nmake install

Building For Symbian On Windows

To configure the Qt Mobility libraries, run configure in the package directory. (-prefix cannot be used since the libraries are installed into the SDK directory)

        cd c:\QtMobility\%DISTNAME%
        configure

Type configure -help to get a list of all available options.

To create and install all the libraries and tools, type:

    make

(Note: no make install step is necessary) The libraries will be deployed into the SDK and will be ready to use for applications running within the emulator.

Rather than building the libraries it is also possible to deploy a prebuilt set of libraries. Under the c:\QtMobility\%DISTNAME%\symbian directory there contains Mobility_tech_preview_libraries.zip. Extract this into the SDK root directory to add the necessary libraries. If you have multiple SDKs then repeat this step for each of them.

To build an SIS package for a particular library such as bearer management run the following commands

    cd src/bearer
    make release-gcce
    createpackage bearer_template.pkg release-gcce

There is also a set of prebuilt SIS file for all the libraries under c:\QtMobility\%DISTNAME%\symbian\Mobility_tech_preview.sis which can be deployed on your device.

Building Individual Qt Mobility Domains

Qt Mobility is comprised of several domains but all of these may not need to be built. To build a single domain, perform the configure step as outlined above, and then perform the make step in the appropriate directory to create the desired library.

The directory structure will look something like

    ./src/bearer
    ./src/contacts
    ...
    ./src/systeminfo

e.g. To build bearer on Unix:

    cd ./src/bearer
    make
    make install

or on Windows:

    cd src\bearer
    nmake
    nmake install

Environment Variables

In order to use QtMobility some environment variables need to be extended to locate the libraries, which are placed in the lib directory of the install path.

On Unix: LD_LIBRARY_PATH should be extended to include: $TARGET_DIR/lib

In .profile (if your Unix shell is bash,ksh,zsh or sh), add the following lines

    LD_LIBRARY_PATH=$TARGET_DIR/lib:$LD_LIBRARY_PATH
    export LD_LIBRARY_PATH

In .login (incase your shell is csh or tcsh), add the following line:

    setenv LD_LIBRARY_PATH=$TARGET_DIR/lib:$LD_LIBRARY_PATH

If you use a different Unix shell, please modify your your environment variables accordingly.

On Windows: PATH should be extended to include: C:\%TARGET_DIR%\lib

For newer versions of windows, PATH can be extended through "Start->Settings->Control Panel->System->Advanced-> Environment variables" and for older versions by editing C:\autoexec.bat

And now the installation is complete, we hope you enjoy using Qt Mobility.


Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies) Trademarks
Qt Mobility Project 1.0.0 (Technology Preview)