![]() |
Home · All Classes · All Functions · | ![]() |
To begin, obtain the most recent distrubution package from http://get.qt.nokia.com
To install Qt Mobility you must already have installed Qt 4.6 or higher, visit http://get.qt.nokia.com to obtain a copy. Furthermore perl must be installed and available in the environment path. Windows environments may require the installtion of a perl interpreter such as ActivePerl.
Qt Mobility Project APIs are comprised of a number of domains. Some of these domains have dependencies and these are outlined below:
API | Dependency | compile time | runtime |
---|---|---|---|
Bearer Management | The Linux backend depends on QtDBus (auto-detected) and NetworkManager, although Bearer Management will compile without them there will be reduced functionality. On Mac, QtBearer depends on CoreWLAN (auto-detected) if Mac OS X SDK 10.6 is available. Functionality will be reduced if CoreWLAN is not available. | N(Y) | N |
Contacts | The Maemo 6 backend depends on libqttracker. Other components offered by the Maemo 6 platform may be required in order to support the full functionality of the Maemo 6 backend. | Y | N |
Location | The 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 |
Messaging | On Linux, QtMessaging depends on qtopiamail from QMF. The Windows Mobile backend depends on ActiveSync version 4.5. While not supported for this release the desktop Windows backend requires that a MAPI subsystem is installed. Note that messaging functionality will not work if you are using the MinGW compiler. 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. | N | Y |
Multimedia | On all platforms, QtMedia depends on QtMultimedia and QtNetwork. On all platforms, QML elements for sound effects and music and video playing are exported if QtDeclarative (auto-detected) is available. On all platforms, additional rendering paths are enabled of QtOpenGL (auto-detected) is available. On Maemo 5, QtMedia depends on PulseAudio if QtDeclarative is used. | ||
Multimedia mediaservice plugins | The audioengine plugin for Unix depends on QtMultimedia. The dsengine plugin for desktop Windows depends on QtMultimedia. The gstengine plugin for Linux and Maemo depends on gstreamer-0.10 (>= 0.10.19), gstreamer-audio-0.10 (>= 0.10.19), gstreamer-base-0.10 (>= 0.10.19), gstreamer-interfaces-0.10 (>= 0.10.19) and gstreamer-video-0.10 (>= 0.10.19). If asound (auto-detected) is available, ALSA device detection will be enabled. The phononengine plugin for Mac depends on phonon. The QtMobilityMultimediaEngine for Symbian depends on QtMultimedia. To enable all mediaservices on symbian one must download sdk plugins. Sdk plugins are available at http://wiki.forum.nokia.com/index.php/SDK_API_Plug-in For 5th edition sdk plugins are installed with installer (all at once), but for FP1 and FP2 devices a zip is provided. You will need following plugins to compile all features: MediaPlayerEngine (MediaPlayerUtilityAPI for 3rd FP2), AudioRoutingAPI , Tuner Utility (only for 3rd FP1) Radio Utility API (for 3rd FP2 and 5th ed), SymbianOnboardCameraAdvancedSettingsAPI(for 3rd FP2 and 5th ed) and autofocus_extension_library_s60_3rd_ed for (3rd FP1 included in the camera example http://sw.nokia.com/id/2f492479-ac8c-4c3e-aa90-cc883e190d83/S60_Platform_Camera_Example_with_AutoFocus_Support_v2_2_en.zip) | Y | N |
Publish & Subscribe | On Linux, QtPublishSubscribe depends on QtNetwork. On Maemo 6, it depends on contextsubscriber-1.0 from Context Kit | Y | N |
Service Framework | On all platforms, QtServiceFramework depends on QtSql. QtSql also needs the SQLite 3 driver (enabled by default) at runtime. | N | Y |
System Information | On all platforms, QtSystemInfo depends on QtNetwork. On Linux, it depends on QtDBus (auto-detected), HAL and NetworkManager, although System Information will compile without them, there will be reduced functionality. It also depends on QtGui. On Mac, it depends on CoreWLAN (auto-detected) if the Mac OS X 10.6 SDK is available. It will compile with older SDK's but there will be reduced functionality. On Maemo, it depends on QtDBus (auto-detected). QtDBus is used to communicate with HAL, and functionality will be reduced if either is unavailable. | N(Y) | N |
QtVersit | On all platforms, QtVersit depends on QtContacts. |
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.
Ensure that all compile time dependencies for your particular platform have been met before building.
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.
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 Qt Mobility for Symbian is not necessary as the package contains pre-built binaries for the SDK and SIS file for the device. See the symbian\install.txt file on how to deploy these.
If you wish to build QtMobility yourself, 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 deploy the libraries and tools for the emulator run:
make debug-winscw
To create the libraries and tools for a device run:
make release-gcce
Note: make install has no meaning for building on Symbian. The libraries will be deployed into the SDK (when running make) and will be ready to use for compiling applications for the emulator and/or device.
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
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 |