Build an environment for getting started with QT for Symbian

Document directory

• Requirements on mobile phones

Qt for the Symbian platform requirements

Qt for the Symbian platform requires the following software installed on your development PC:

• Carbide. c ++ v2.0.0 or higher
  • Note:

    It may be necessary to update the carbide compiler. See here

    For instructions how to check your compiler version and how to patch it, if needed.

• ActivePerl v5.6.1 build 638
  • Note:

    According to Symbian, version 5.6.1 build 638 is mandatory. Using later versions may result in unexplained errors.

• S60 Platform SDK 3rd edition FP1 or higher
  • Note:

    UsersS60 Platform SDK 3rd edition FP1

    Also need special update. The update can be found here

    .

• Open C/C ++ v1.6.0 or higher

  . Install this to all Symbian sdks you plan to use QT.

• Building QT tools from scratch requires mingw 3.4.5 or higher

  , Or another Windows compiler.

  • Note:

    This is not required if you are using pre-built Binary Package.

• Building QT libraries requires rvct

  2.2 [Build 686] or later, which is not available free of charge.

Running QT on real device requires the Open C to be installed on the device. The Open c installation packages are embeddedQt_installer.sis

,
Which is already ded in QT for Symbian Binary Package. If you are building
Qt from scratch, you can find the required packages in the Symbian SDK
Where you installed Open C/C ++:

• Nokia_plugin/openc/s60opencsis/pips_s60 _ <version>. Sis

• Nokia_plugin/openc/s60opencsis/openc_ssl_s60 _ <version>. Sis
• Nokia_plugin/opencpp/s60opencppsis/stdcpp_s60 _ <version>. Sis

If you wish to do hardware debugging with carbide or run
Applications in real devices using "Make run" command, TRK must be
Installed to the device.Note:

TRK is not required if you just want to install and run applications manually on the device.

Application TRK

. Choose
The correct installation package based on the s60 version of your
Device (s60 _ <S60-version> _ app_trk _ <TRK-version>. sisx ).

Web: http://doc.trolltech.com/4.6-snapshot/requirements-symbian.html

 

Frequently Asked Questions (FAQ) for Qt for symbianq: Do you support carbide. c ++ v1.2?

A: No. Recommended carbide version to use is 2.0.2 and up.

Q: Which sdks are supported?

A: QT has been tested with the s60 3.1, 3.2, 5.0 and n97 SDK.

Q: What tools do I need to develop an application with QT for Symbian?

A: see http://doc.trolltech.com/4.6-snapshot/requirements-symbian.html

Q: What platforms does QT for Symbian support?

A: see readme. Symbian file.

Q: Which QT modules are currently working on Symbian?

A: see readme. Symbian file.

Q: Which new QT modules are coming in the next release?

A: guid

Q: When is the next release?

A: guid

Q: Which parts are currently left out of qtcore?

A: qtconcurrent not ported, qprocess doesn't support streams, and
Qsettings not using Symbian specific storages I. e. Central Repository

Q: Which parts are currently left out of qtgui

A: printing and accessibility.

Q: Which parts are currently left out of qtnetwork?

A: no support for IPv6 and no support for multicast.

Q: What input methods are supported in the current release?

A: multitap and predictive text in any language, as well as virtual keyboard on touch based devices.

Q: Which devices has colossus release been tested on?

A: n78, N79, N95, n96, n97, 5800 xpressmusic and 6290

Q: I'm getting an error when trying to run example.exe, can you help me?

A: Before sending email to feedback list please check that you have
Set your enviroment variables correctly and that you have patched your
Environment according to installation notes.

Make sure you have patched your x86 compiler by typing in Command Prompt:

Mwccsym2.exe-version

Expected output is:

Version 3.2.5 build 482 (build 482)

The build number shoshould be 482 or later.

Q: I give up. I need help from the mailing list. What shoshould I include?

A: When sending email to feedback list please include the following information in your post:

1. Executable that you are trying to run.
2. Environment that you are working with e.g. s60 5.0 v.1.0
3. Call Stack of the error occuring, see section the question about how to obtain call stack from carbide.

Q: How do I get call stack from carbide 2.0?

A: First you need to import your project to carbide in order
Debug it. Select File-> Import-> Symbian OS bld. inf
File if you can't find bld. inf under your project directory you first
Need to run bldmake bldfiles from command prompt. In order to catch all
Errors occuring you need to check all but C ++ exceptions under x86
Exceptions tab in debug configurations. When running debug carbide will
Stop at the point of error occuring. From debug view select the call
Stack under thread saying suincluded and copy (CTRL + C) it and paste it
To the email you are about to send.

Q: How do I load my plugin? I tried loading it from/sys/bin but it fails.

A: In QT for Symbian we had to implement plugin stubs to get around
The need for allfiles capability to access/sys/bin and some other
Issues. plugin stubs are files with the same base name as the actual
Plugin DLL but with a ". qtplugin" suffix. They need to be in some
Accessible location. For private plugins this is typically
Application's private Dir, but for public plugins it can be anywhere;
E.g. QT extension plugins have default public base dir
"/Resource/QT/plugins" (which can be queried
Qlibraryinfo: location (qlibraryinfo: pluginspath, if needed at compile
Time, or via the $ qt_plugins_base_dir variable defined in
Data_caging_paths.prf feature file, if needed in the. Pro file). If
Either the stub or the actual plugin. dll are missing, the plugin
Loading will fail. The stub contents are mostly irrelevant. Only
File Name and timestamp matter (the stub timestamp is checked in plugin
Caching). If the deployment variable is used properly, the stub gets
Generated and deployed automatically and you don't need to worry about
It. See http://doc.trolltech.com/4.6-snapshot/qmake-variable-reference.html#deployment

For details.

When loading plugins with qpluginloader, do not give the plugin DLL
Itself as a target, use the stub file instead, although for convenience
You can use either ". dll" or ". qtplugin" as the suffix. E. g. if you
Have the plugin stub named as "C:/Foo/bar. qtplugin", and the actual
Plugin as is located at "C:/sys/bin/bar. dll", you can use either
Qpluginloader ("C:/Foo/bar. dll") or qpluginloader ("C:/Foo/bar. qtplugin ")
To load the plugin. So basically you can treat the stub as you wowould
The actual plugin on other platforms.

Q: QT applications get an additional white window with a black cursor. How can I fix this?

A: This is a result of having the 'stdserver' package installed.
This application is a server process that redirects stdin and stdout
A console window by default. This behavior can be changed
Modifying the configure file located at "C:/system/data/config. ini ".
The relevant change involves editing the [stdio] section and changing
Stdin and stdout to be:

     STDIN = MEDIA1
     STDOUT = MEDIA4

Media1 and media4 shoshould be of the type 'file' and shoshould have
Path pointing to catalog in.txt "or catalog out.txt" respectively and located in
Same directory as "config. ini". You must also ensure that the specified in.txt"
File actually exists when making the above change. The above change
Will work both in the emulator as well as in hardware where the path
Inside the SDK is $ epocroot/winscw/C/system/data.

Q: Installing QT on n78 with firmware PR 1.0 fails. How can I work around it?

A: Please upgrade device's firmware to a newer release.

Q: When installing "qt_installer.sis" or "qt_demos.sis" it fails with error "-16". How can I work around it?

A: Try installing it again. If that fails, try installing the Open C packages + "QT. Sis" + "qtwebkit. Sis" one by one.

Web: http://qt.gitorious.org/qt/pages/SymbianFAQ

 

The above information was not found before I installed QT. I copied the information and gave it to the users. I also gave it to myself in the future.

If you need Nokia
To run the QT program on the s60 series mobile phones, you need to first have the QT Runtime Library, because the QT library is not installed when the store sells your mobile phone (maybe later versions will be installed, but who knows how many future
So you need to install it yourself. Of course, the QT library will also depend on several other C and C ++ libraries, namely pips, openc_ssl, and stdcpp. For example, 4.5.2, basic
The library can be pips_s60_rj5_5b.sis.

Openc_ssl_s60_rj5_5b.sis

Stdcpp_s60_rj5_5b.sis

. Download the QT library and demo program in

Http://pepper.troll.no/s60prereleases/demos/

Directory. After installation, you can experience the QT application on your mobile phone.

If you want to test your own Qt-4.6.0-beta program, You Need To Qt-4.6.0 the library files above, I prompt to QT when installing your own application
4.0.6 or later versions are not bugs. I have reviewed the documents in http://pepper.troll.no/s60prereleasesseveral times.
The location for downloading the Qt-4.6.0-beta library was not found. I had to help myself. If you have installed QT for Symbian
4.6.0-beta SDK, you can see two. sisfile fluidlauncher. Sis and
Qt. Sis, you need to install them. Similarly, the QT dependency library can be found in the installation directory at <epocroot> nokia_plugin/openc/s60opencsis/pips_s60 _ <version>. sis <epocroot> nokia_plugin/openc/s60opencsis/openc_ssl_s60 _ <version>. sis <epocroot> nokia_plugin/opencpp/s60opencppsis/stdcpp_s60 _ <version>. sis

 

Note:

1. If you find that there are no packages installed on your mobile phone, or the compilation fails, for example, if I didn't install Open c ++ on s60 3th. Latest download

2 carbide requires a later version. Latest download

3. Add the bin path (C:/qts60/bin) of QT to the system path.

4. Add the QT path to carbide: window-> preference-> QT

 

Refer:

Install QT on s60
Getting started with QT for s60