              
Installation GuideGet the Qt Mobility API PackageTo begin, obtain the most recent distribution package from http://get.qt.nokia.com Pre-requisites & DependenciesTo install Qt Mobility you must already have installed Qt 4.6 or higher, visit http://get.qt.nokia.com to obtain a copy. However Mobility's QML components are not enabled unless Qt 4.7 or higher is used. Furthermore perl must be installed and available in the environment path. Windows environments may require the installation of a perl interpreter such as ActivePerl. On the Maemo 5 (Fremantle) platform PR1.2 firmware release or newer is required, and the Qt 4.7 packages are required. Qt Mobility Project APIs are comprised of a number of domains. Some of these domains have dependencies and these are outlined below:
UnpackingUnpack 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(prefix) must not contain any spaces. BuildingEnsure that all compile time dependencies for your particular platform have been met before building. If Qt is installed for multiple platforms it is also important to ensure that the correct version of qmake is being used. Note: Static builds of Qt are not supported by Qt Mobility. Building On UnixTo 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 WindowsTo 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. To create and install the libraries and tools from a Microsoft Visual Studio command prompt, type: nmake nmake install Building For Windows CEThe process is much the same as for Windows, although it is important to run the setcepaths script from the bin directory of the Qt for Windows CE installation to ensure that the correct headers and libraries are used. Building For Symbian On WindowsBuilding 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 INSTALL.symbian file on how to deploy these. The file is located in the root directory of the package. 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 using the commercial compiler RVCT for a device, run: make release-armv5 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. Building For Mac OS XThe process is the same as for Unix, with the additional configuration option of -sdk /Developer/SDKs/MacOSX10.5.sdk to specify an Apple SDK version other than the default. Note: QtMobility currently has no support for building with Xcode. Note: QtMobility will be built using the same frameworks configuration option that Qt was built with. Building Individual Qt Mobility ModulesQt Mobility is comprised of several modules but all of these may not need to be built. To specify which modules should be built, use the -modules switch with the configure script when performing the configure step as outlined above. e.g. To build just the bearer module: configure -modules bearer If multiple modules are required the module names should be separated by a space and surrounded by double quotation marks. If a selected module depends on other modules the dependencies will be enabled automatically. .e.g. To build just the bearer and location modules: configure -modules "bearer location" Type configure -help to see the names of the available modules. Making the libraries available to applicationsIn 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. Making the libraries available on UnixThe environment variable 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. Making the libraries available on WindowsThe environment variable 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 Making the libraries available on Windows CEEnvironment variables do not exist on Windows CE, and so users of Qt Mobility for Windows CE have to do things slightly differently. A pre-requisite for Qt Mobility applications is that the Qt libraries and plugins have been deployed as per Qt's documentation. The deployment of the libraries to the device is normally done with Microsoft Visual Studio or Microsoft ActiveSync. The libraries can be made globally available by deploying them to C:\Windows on the device, or can be deployed once per application by copying them into the same directory as the executable. Mobility expects plug-ins in the subdirecty plugins/<APIname> in one of the locations specified by QCoreApplication::libraryPaths() which includes C:\Windows and the Mobility application's directory. And now the installation is complete, we hope you enjoy using Qt Mobility. X
|
