Editing Qt4 development

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

'''IMPORTANT: This page is for Fremantle PR 1.2 using Qt 4.6 or higher.'''
'''If you want to develop for Diablo or use Qt 4.5 please have a look at the [[Qt4_Hildon_Legacy|Qt4 Hildon Legacy Page]].'''

== Introduction ==

To develop with [[Qt-Maemo|Qt for Maemo]], a working SDK installation is required. There are [[Documentation/Maemo_5_Final_SDK_Installation|instructions on how to install the Maemo SDK]], and you can [http://www.youtube.com/watch?v=c8myh_iBy8k watch the Maemo SDK in action]. Alternatively, you may want to try [[MADDE]], a cross-platform Maemo development tool, available as a technology preview.

Maemo 5 has [http://doc.qt.nokia.com/qt-maemo-4.6/index.html official Qt documentation] - especially see [http://doc.qt.nokia.com/qt-maemo-4.6/examples-maemo5.html the Maemo5 Qt examples page].

== Getting started ==

To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation|install the Maemo SDK]].

Qt is available in public Fremantle repository since the release of [[Maemo 5/PR1.2|PR1.2]]. To upgrade older Scratchbox targets to use the latest packages, execute the following commands (inside Scratchbox):
 fakeroot apt-get update
 fakeroot apt-get dist-upgrade

You can install Qt with the command:
 fakeroot apt-get install libqt4-dev

'''GIANT WARNING''': Your device might not be running Qt 4.6, but your Scratchbox probably is.  Make sure that your N900 has at least the PR1.2 update by checking the software version (found in Settings->About product. PR1.2 is version 10.2010.19-1).

===How to compile a Qt application in Scratchbox===

Qt applications are usually built using QMake. Some projects, like KDE, use CMake, for more flexibility.
 
==== QMake ====
[http://doc.trolltech.com/qt-maemo-4.6/qmake-manual.html QMake] is a tool that helps simplify the build process for development project across different platforms

You can build your Maemo Qt application in 3 simple steps:
# Generating project file (Required if there is no .pro file into the app source tree)<pre>qmake -project</pre>
# Generating Makefile from the QMake project file:<pre>qmake file.pro</pre>
# <pre>make</pre>

==== CMake ====

CMake projects usually have a <code>CMakeLists.txt</code> file instead of: 
# .pro file used by QMake projects
# <code>Makefile.am</code> used by Autotools projects (standard in Unix/Linux)

Using CMake to build the project is extremely easy. In the directory containing <code>CMakeLists.txt</code>, supply the following two commands, where path is the path to the source code.
 cmake path
 make

Note: CMake is not installed by default in [[:Category:Scratchbox|Scratchbox]]. You can install it with the command:
 fakeroot apt-get install cmake

=== Running a Qt application in: ===
==== Scratchbox ====
Diablo and Fremantle Qt applications can run on the device as in Scratchbox.

First step to run a Qt application is starting the SDK UI:
 
# Run Xephyr on your host (not in Xephyr!). It is able to run a [[:wikipedia:X_Window_System|X Server]] inside another X Server.<pre>Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb</pre>
# Inside Scratchbox, set the display for applications:<pre>export DISPLAY=:2</pre>
# You can now run the SDK UI. A Diablo or Fremantle desktop will appear in your Xephyr window:<pre>af-sb-init.sh start</pre>
# Now you are ready to run any Maemo or Maemo Qt application with:<pre>run-standalone.sh ./qtapps</pre>

Note: <code>run-standalone.sh</code> sets some variable needed by Qt to use the Hildon style.

Hint: If you don't want to run run-standalone.sh all the time, you can also source it: <pre>source /usr/bin/run-standalone.sh</pre> In that shell, you can then run Qt applications without calling run-standalone.sh on every start.

==== Device ====
Maemo Qt applications are Linux binaries. They can run on the device without any problem if you copy them to "partitions" mounted with exec flag. (for example, <code>/home/user</code> or <code>/opt</code> in Fremantle).

For example, if we want to run quassel (Qt IRC Client), we have to launch it with:
 su -c ./quassel user

== Porting Qt applications to Maemo ==

Porting a Qt desktop application to Maemo requires very little effort. This is because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.

===Overriding the Qt Maemo changes===

====Maemo Style====

Hildon Style is the default Qt application style. Other style available are:
* [http://doc.trolltech.com/qt-maemo-4.6/gallery-cleanlooks.html QCleanLooks]
* [http://doc.trolltech.com/qt-maemo-4.6/gallery-windows.html Windows]
* [http://doc.trolltech.com/qt-maemo-4.6/gallery-plastique.html Plastique]

Qt application can use other Qt styles;
* Running your application with the style flag:<pre>./qt-test-application -style windows</pre>
* Using [http://doc.trolltech.com/qt-maemo-4.6/qapplication.html#setStyle QApplication::setStyle( QStyle * style )]
* If you want to change the style of a widget: [http://doc.trolltech.com/qt-maemo-4.6/qwidget.html#setStyle QWidget::setStyle( QStyle * style )]

====Showing the status bar====

Hildon applications don't have a status bar. Qt for Maemo hides the status bar by default.

You can show it again by using method <code>statusBar()->show()</code> in your class derived from <code>QMainWindow</code>.

===Adding Maemo changes to a Qt Application===

Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives:

In the source code:

<source lang="cpp">
#ifdef Q_WS_MAEMO_5
 //specific hildon/maemo5 code here
#endif
</source>

In the project file:

<pre>
maemo5 {
 message("Hello Hildon")
 SOURCE += hildon.cpp
 HEADER += hildon.h
 FORMS += hildon.ui
}
</pre>

=== Home widget interaction ===

== Debugging a Qt application ==

{{main|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}

'''Note''': Fremantle Gdb 6.8 crashes in x86 and gives messed up backtraces on the device. Using gdb 7.0 is recommended. You can get gdb 7.0 sources from http://ftp.de.debian.org/debian/pool/main/g/gdb/gdb_7.0.orig.tar.gz, compile it (./configure && make) inside X86 and armel scratchbox targets.
[http://chaos.troll.no/~harald/gdb7/ Here you can find GDB7 for fremantle x86 and armel]. 
 /usr/local/bin/gdb7 ./myapp

== Profiling a Qt application ==

=== OProfile ===

=== Valgrind ===

== Packaging a Qt application for Maemo ==

== Maemo Qt API Reference ==

Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well. To Develop a Qt application you can use the [http://qt.nokia.com/doc/qt-maemo-4.6 Official Qt 4.6 for Maemo API documentation] and the list below to see what are the Maemo changes.

Here are examples that show several Maemo 5 Qt widgets in Qt.

* http://qt.nokia.com/doc/qt-maemo-4.6/examples-maemo5.html
* http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/4.6-fremantle/examples/maemo5/widgets

===Maemo5 Readme file===

There is a [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 README file in Qt source tree].

== Contributing to the Maemo Qt Project ==

Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.

Here there is a list of things that every person interested in helping us should read.

===Stay updated===

Any Maemo Qt developer should be updated and should participate to the discussions, for that he must join the Mailing list. BTW the mailing list is not for Maemo Qt Developers but it's open to Maemo Qt application developers too.

=== Introduction to Git ===

If you are a git newbie you maybe find interesting these links:
* http://www.sourcemage.org/Git_Guide
* http://www.gitcasts.com/
* http://www.gnome.org/~newren/eg/git-for-svn-users.html
* Using the git protocol through a HTTP CONNECT proxy: http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/

===Understanding the structure of our Git repository===

=== Preparation ===

Make sure each scratchbox target has

fakeroot apt-get build-dep libqt4-gui

(you may need to apt-get install libgl-dev too as it's not in the Build-Depends: yet)

===Building Qt from Git repository===

# Make sure you have all the build dependencies: <pre>fakeroot apt-get build-dep qt4-x11</pre>
# Clone the repository: <pre>git clone git://gitorious.org/+qt-developers/qt/x11-maemo.git qt-maemo</pre> 
# Change dir: <pre>cd qt-maemo</pre>
# Configure Qt: For x86 targets:<pre>./configure -maemo5</pre> For ARM targets:<pre>./configure -maemo5 -opengl es2</pre>.
# Build Qt: <pre>make</pre>
# Install Qt: <pre>make install</pre>

===Merging branches changes in the mainline [OLD]===

Before to merge your changes in the mainline, the code must be full working, cleaned and tested. A review from another developer is also needed in order to reduce the possibility to add errors.

===QML===

[[QML]] is a GUI interface building scripting language for Qt. Check out the [[QML-EnhancedCalcExample | QML calculator example]].

==F.A.Q.==

; ''I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong?''
: <pre>/targets/FREMANTLE_X86/usr/include/qt4/QtCore/qatomic_i386.h:127: error: impossible constraint in 'asm'</pre>
:You are using x86 include files, then you have to update your Makefile. Running <code>qmake</code> before <code>make</code> will be solve this issue.

; I'm trying to compile a Qt packcage for x86, but I got the error below. What's wrong?
: <pre>In file included from maemo/gconfsymbols.cpp:41:
 maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory</pre>
: Your scratchbox does not have <code>/bin/sh</code>, so when calling <code>pkg-config</code> from <code>qmake</code>, <code>CFLAGS</code> and <code>LIBS</code> are not set correctly. Running <code>ln -s /scratchbox/tools/bin/sh /bin/sh</code> will be solve this issue.

; I'm trying to compile a diablo Qt package, so I just created a symbolic link, debian, for debian.diablo, and then run dpkg-buildpackage command, but I got a build error because the symbolic link was deleted
: When running dpkg-buildpackage, all symbolic links will be deleted, so need to rename the folder from debian.diablo to debian to make a build of diablo Qt package.

; I installed Qt (libqt4-dev) to scratchbox and tried to build a sample application, but I got the error because some header files such as qhildonstyle.h, and qvfbhdr.h etc. were missing
: libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.
: <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>

[[Category:Development]]
[[Category:Qt]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Main (view source) (protected)

Retrieved from "https://wiki.maemo.org/Qt4_development"

Personal tools

Navigation

Views

Editing Qt4 development

@@ Line 212: / Line 212: @@
   maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory</pre>
 : Your scratchbox does not have <code>/bin/sh</code>, so when calling <code>pkg-config</code> from <code>qmake</code>, <code>CFLAGS</code> and <code>LIBS</code> are not set correctly. Running <code>ln -s /scratchbox/tools/bin/sh /bin/sh</code> will be solve this issue.
+; I'm trying to compile a diablo Qt package, so I just created a symbolic link, debian, for debian.diablo, and then run dpkg-buildpackage command, but I got a build error because the symbolic link was deleted
+: When running dpkg-buildpackage, all symbolic links will be deleted, so need to rename the folder from debian.diablo to debian to make a build of diablo Qt package.
 ; I installed Qt (libqt4-dev) to scratchbox and tried to build a sample application, but I got the error because some header files such as qhildonstyle.h, and qvfbhdr.h etc. were missing