Maemo Wiki Mirror - User contributions [en]

Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Programming Environments/Using Maemo 5 specific APIs in Qt application

2010-01-17T21:56:53Z

88.115.28.145: /* Using Zoom In and Zoom Out keys */

= How to use Maemo 5 specific APIs from Qt application =

== Accelometer ==

=== Introduction ===

This section explains how to use the [[Accelerometers | accelerometer]] D-Bus interface in a Maemo 5 Qt application.

The following code examples are used in this section:
* [https://garage.maemo.org/svn/maemoexamples/trunk/qt-maemo-gravity-example/ qt-maemo-gravity-example]

=== D-Bus interface ===

It is up to each application how to organize interactions with the [http://maemo.org/api_refs/5.0/beta/mce-dev/ MCE] orientation interface. In [[Documentation/Maemo 5 Developer Guide/Porting Software/Porting Existing GTK+ Application to Maemo 5#Portrait Mode | some cases]] catching orientation signal can be enough, but if, e.g., more frequent updates are needed, you might want to use method calls, as demonstrated in our example.
We've moved D-Bus related functionality and orientation based calculations to a separate library that implements `DeviceOrientationNotifier' class.
Our notifier asks MCE about orientation parameters with a certain period,
void DeviceOrientationNotifier::timerEvent(QTimerEvent *)
{
QDBusMessage msg = QDBusMessage::createMethodCall(MCE_SERVICE, MCE_REQUEST_PATH, MCE_REQUEST_IF, MCE_DEVICE_ORIENTATION_GET);
bool sent = QDBusConnection::systemBus().callWithCallback(msg, this, SLOT(mceOrientationSlot(QString, QString, QString, int, int, int)));
}
processes answers in `mceOrientationSlot', and emits data needed by the application with the following signal.
void deviceOrientation(qreal pitch, qreal roll);

=== Example application ===

We've modified [http://qt.nokia.com/doc/4.5/graphicsview-collidingmice.html one of Qt4 Examples] in order to show how device orientation can be used.
In our case pitch and roll are scene's characteristics, so we've implemented a `SceneTuner', whose slot can be connected to an appropriate signal in order to setup these scene properties.
DeviceOrientationNotifier notifier(100);
SceneTuner tuner(&scene, TimerInterval);
QObject::connect(&notifier, SIGNAL(deviceOrientation(qreal, qreal)), &tuner, SLOT(setProps(qreal, qreal)));
Based on that each mouse can take into account the gravity effect, see `Mouse::advance' for details.

== Using Zoom In and Zoom Out keys ==

This section uses the same qt-maemo-gravity-example to explain how to use Zoom In and Out keys in a Qt application. They are used to set the application window to fullscreen and normal modes like in the GTK+ example [[Documentation/Maemo 5 Developer Guide/Porting Software/Porting Existing GTK+ Application to Maemo 5|Maemo Sliders]].

First, the keys are released from maemo-status-volume by using <code>XChangeProperty()</code>.

hardkeyhandler.cpp:
void HardkeyHandler::grabIncreaseDecreaseKeys(QWidget* window, bool grab)
{
// Tell maemo-status-volume to grab/ungrab increase/decrease keys
unsigned long val = (grab==true)?1:0;
Atom atom;
atom = XInternAtom( QX11Info::display(), "_HILDON_ZOOM_KEY_ATOM", 0);
XChangeProperty (QX11Info::display(),
window->winId(),
atom,
XA_INTEGER,
32,
PropModeReplace,
(unsigned char *) &val,
1);
}

Next, a handler for keypresses is created. 73 and 74 are the keycodes for F7/F8 in the SDK and Zoom In/Out buttons in the device. Handler functions emit corresponding signals when called.

hardkeyhandler.cpp
bool HardkeyHandler::processX11Event(XEvent* event)
{
if ( event->type == KeyPress )
{
if (event->xkey.keycode == 73 || event->xkey.keycode == QKeySequence::ZoomOut)
{
emit decreaseKeyPressed();
return true;
}
else if (event->xkey.keycode == 74 || event->xkey.keycode == QKeySequence::ZoomIn)
{
emit increaseKeyPressed();
return true;
}
}

return false;
}

Signals need slots, of course. They are located to myapplication.h and myapplication.cpp files. Here changing to fullscreen and back are done by <code>showFullScreen()</code> and <code>showNormal()</code>.

myapplication.cpp
void MyApplication::increaseKeyPressed()
{
qDebug("MyApplication::increaseKeyPressed");
view.showFullScreen();

}

void MyApplication::decreaseKeyPressed()
{
qDebug("MyApplication::decreaseKeyPressed");
view.showNormal();
}

The new signals are connected to corresponding slots in <code>main()</code>.

main.cpp
QObject::connect(app.keyHandler(), SIGNAL(decreaseKeyPressed()), &app, SLOT(decreaseKeyPressed()));
QObject::connect(app.keyHandler(), SIGNAL(increaseKeyPressed()), &app, SLOT(increaseKeyPressed()));

Finally, gtk-x11 library and the new source and header files (hardkeyhandler.* and myapplication.*) are added to the Qt project file:

collidingmice-gravity.pro:
LIBS += -ldevornot-qt-maemo -L/usr/local/lib -lgtk-x11-2.0

HEADERS += \
mouse.h \
hardkeyhandler.h \
myapplication.h \
scenetuner.h
SOURCES += \
main.cpp \
hardkeyhandler.cpp \
myapplication.cpp \
mouse.cpp

Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Programming Environments/Using Maemo 5 specific APIs in Qt application

2010-01-17T21:56:07Z

88.115.28.145: /* Using Zoom In and Zoom Out keys */

Packaging a Qt application

2010-01-15T21:18:02Z

88.115.28.145: /* Editing the Control file */

= Packaging a Qt application for Maemo=
== Finding your package in debian ==
If you want to port a Qt package to Maemo, you should check and see if it is already packaged for debian and use that package if you can - this will save you time and effort. You can search in debian's [http://www.debian.org/distrib/packages Package Tracking System (PTS)] to see if it is there. There is a search system on the PTS page, under the "distribution" drop-down, select 'any', this will search throughout debian's repositories to find the package. Debian has more than 20,000 packages just in its stable distribution so your application is likely already packaged.

If you find the package already exists in debian, you can get the source, including the packaging source, with apt-get. To do this, you'll have to edit your /etc/apt/sources.list, you can follow this recipe;

<pre>
$ echo “deb http://ftp.it.debian.org/debian/ unstable main contrib non-free” >> /etc/apt/source.list
$ apt-get update
$ apt-cache search "application name"
$ apt-get source "application name"
</pre>

''To learn more about the /etc/apt/sources.list you can do a 'man sources.list' if you are running debian or a debian based GNU/Linux distro.''

== Porting the debian package to a Maemo package ==
If your application has been already packaged for debian, you can begin your maemo packaging with this section. Once you have the source of the debian package, you will need to make some modifications to that package for it to build under Maemo. For the complete Maemo Package Policy, use [http://maemo.org/forrest-images/pdf/maemo-policy.pdf this link] to a pdf.

In order to create a new package for maemo, you'll need to:
* Rename the upstream source directory in Package-Version (eg: myapp-0.1)
* Create “src” directory in Package-Version/
* Copy all the files in the src/
* Rename src/appname.pro in src/src.pro
<pre>
$mv myapp myapp-0.1
$cd myapp-0.1
$mkdir src
$cp * src
$mv src/appname.pro src/src.pro
</pre>

Append the following chunk to end of your src/src.pro . The chunk adds install section to your qmakefile

<pre>
unix {
#VARIABLES
isEmpty(PREFIX) {
PREFIX = /usr/local
}
BINDIR = $$PREFIX/bin
DATADIR =$$PREFIX/share

DEFINES += DATADIR=\"$$DATADIR\" PKGDATADIR=\"$$PKGDATADIR\"

#MAKE INSTALL

INSTALLS += target desktop iconxpm icon26 icon40 icon64

target.path =$$BINDIR

desktop.path = $$DATADIR/applications/hildon
desktop.files += $${TARGET}.desktop

iconxpm.path = $$DATADIR/pixmap
iconxpm.files += ../data/maemo/$${TARGET}.xpm

icon26.path = $$DATADIR/icons/hicolor/26x26/apps
icon26.files += ../data/26x26/$${TARGET}.png

icon40.path = $$DATADIR/icons/hicolor/40x40/apps
icon40.files += ../data/40x40/$${TARGET}.png

icon64.path = $$DATADIR/icons/hicolor/64x64/apps
icon64.files += ../data/64x64/$${TARGET}.png
}
</pre>

*Create a myapp-0.1/myapp.pro file like this:
<pre>
QMAKEVERSION = $$[QMAKE_VERSION]
ISQT4 = $$find(QMAKEVERSION, ^[2-9])
isEmpty( ISQT4 ) {
error("Use the qmake include with Qt4.4 or greater, on Debian that is qmake-qt4");
}

TEMPLATE = subdirs
SUBDIRS = src
</pre>
*Run dh_make to debianize the source archive, it creates:
**An archive with the unchanged upstream source (orig.tar.gz)
**Some basic files in the debian directory
**Some example files (*.EX *.ex)
<pre>
dh_make --createorig --single -e maintainer@email.org -c gpl
</pre>

== Having a look inside the debian/ dir ==
At this point the directory my-app contains
* the source directory ( src/ )
* the debian directory (debian/)

Inside the debian dir we have the files needed for the creation of the debian package
* Changelog - Application's change log
* Compat - Debian helper compatibly version
* Control - Describes the packages to be made
* Copyright - Copyright text
* Rules - A binary makefile containing the rules to build the package

== Maemo Packaging Policy ==
Maemo packages follow the Debian Policy, but there are some items where Maemo:
* Is more strict (it is an embedded distribution)
* Is more relaxed
**Only a target device (Nokia Internet Tablet)
**Only a specified UI (Hildon)
**Only one user.
*Differs from Debian because Maemo has different:
**Objectives
**Maintainers
**Infrastructure

==Editing the Control file ==
Basically it specifies for each package (source or binary) a name, some dependencies, a description etc...
For a Maemo package these fields are very important:
* [http://wiki.maemo.org/Task:Package_categories#Translations Section]: Only the packages in the user segment are showed by App Installer.
* Maintainer: This field MUST be changed if the upstream package is modified
* XB-Maemo-Icon26: It contains the PNG icon encoded in base64 visible in the Application Installer

If you need to encode your icon as base64, there are [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package instructions here.]

<pre>
Source: my-application
Section: user/valid_subsection
Priority: optional
Maintainer: name surname <xxxxxxx.xxxxxx@maemo.org>
XSBC-Original-Maintainer: name surname <yyyyy.yyyyy@debian.org>
Build-Depends: debhelper (>= 5), libqt4-dev, OTHERS_BUILD DEPENDECIES
Standards-Version: 3.7.3

Package: my-application
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: A simple test application
A very simple application with a short description.
Which spans multiple lines actually.
XB-Maemo-Icon-26:
iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAYAAACpSkzOAAAABmJLR0QA/wD/AP+g
vaeTAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH1gURDQoYya0JlwAAAU9J
REFUSMftlL1KA0EUhb/NZl/ggnHQxsJUxt5CUucVJCCkDfgyKdIGG5/A0s5HEBtJ
EdDAQGBgmw0YJmMzgXXYza5CtNkDW9zZw5z7c+ZCgwb/Ai3i9sVl/Bq8RIs4LRK1
gJDsKvJyNXmJMuYTsMoY1zpgozaABdYArQNPZQ1kfyGU7SpqVwxzAMwABWhgpIwp
4vWBB+AUWAI3ypjnfEXtPU4bLKx9vErTeCeiRSYF+fTn1j5dp2myE9EiU+DSi3wX
ymeqRQAmZ3EcA5E/fgO6BULT8zhOcrwXoJdrXRa2Lgps2y2odAUcBUIXQdz78YyC
SldAp8b7+bXrIv91qjZBietqCc2DjbAt4b2WxJkyZljVujlwp0U0cPxuLcAIuC+4
dKxFlsDJarvdAGP/b6hFnDImYs+uG3hbO2AB3Jbsur63tQM+fFx3bzZocEB8AdV2
gJBZgKTwAAAAAElFTkSuQmCC

Package: my-application-dbg
Section: devel
Architecture: any
Depends: my-application (= ${binary:Version})
Description: Debug symbols for a simple test application
Debug symbols for a very simple application, which allow
tracing and debugging.
</pre>

Valid subsections are:
* accessories
* communication
* games
* multimedia
* office
* other
* programming
* support
* themes
* tools

== Editing the rules file ==
The rules file generated by dh_make will be modified in order to look like this one.
We are using qmake, so we haven't a configure file to run.
If you cut-and-paste following file, notify that empty space beginning of lines it TAB characters, it is not multiple space characters. If you cut-and-paste
the following chunk, you most propably get spaces instead tabs and the file does not wok

<pre>
#!/usr/bin/make -f
APPNAME := my_app_name
builddir:
mkdir -p builddir

builddir/Makefile: builddir
cd builddir && qmake-qt4 PREFIX=/usr ../$(APPNAME).pro

build: build-stamp

build-stamp: builddir/Makefile
dh_testdir
# Add here commands to compile the package.
cd builddir && $(MAKE)
touch $@

clean:
dh_testdir
dh_testroot
rm -f build-stamp
# Add here commands to clean up after the build process.
rm -rf builddir
dh_clean
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs

# Add here commands to install the package into debian/your_appname
cd builddir && $(MAKE) INSTALL_ROOT=$(CURDIR)/debian/$(APPNAME) install
# Build architecture-independent files here.
binary-indep: build install
# We have nothing to do by default.

# Build architecture-dependent files here.
binary-arch: build install
dh_testdir
dh_testroot
dh_installdocs
dh_installexamples
dh_installman
dh_link
dh_strip --dbg-package=my-application-dbg
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dh_gencontrol
dh_md5sums
dh_builddeb

binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install configure
</pre>

== Editing the Changelog file ==
It is the log of the changes for a specified application version. It's important file because it sets the binary/binaries and the source packages version and revision.
If an upstream package is re-packaged or modified for maemo, the Maemo revision string should be appended to the upstream revision.
So if in Debian the package name was something like "Myapp-0.4-2" in maemo this package will be called "Myapp-0.4-2maemo0".
The number after the "maemo" string is a progressive number.

== Application menu icon & position ==
The Maemo application menu detects automatically an app that provides a .desktop file in /usr/share/application/hildon . If you don't have desktop file, create one in the src directory.

<pre>
[Desktop Entry]
Encoding=UTF-8
Version=0.1
Type=Application
Name=myapp
Exec=/usr/bin/myapp
Icon=myapp
X-HildonDesk-ShowInToolbar=true
X-Osso-Type=application/x-executable
</pre>

Maemo menu structure is completely different from Debian:
* An unmodified Debian package installs the proper .desktop in /usr/share/applications
* Applications that use the debian menu are displayed in the extra menu

In order to show our application in the correct Maemo menu:
* debian/myapp.install moves the .desktop file and icons in the right directory
<pre>
src/*.desktop usr/share/applications/hildon
src/*.png usr/share/icons/hicolor/26x26/apps
</pre>

* debian/postinst should call maemo-select-menu-location utility to permit the user to choose the menu location. '''This works only in Diablo, it doesn't work in Fremantle.'''
<pre>
#!/bin/sh
maemo-select-menu-location myapp.desktop
</pre>

== Checking Maemo Packages ==
Lintian dissects Debian packages and reports bugs and policy violations.
It contains automated checks for many aspects of Debian policy as well as some checks for common errors.
Unfortunately it doesn't check conformance to the additional Maemo policy.

Currently Maemo is creating [http://maemian.garage.maemo.org/ Maemian] to check its policy.

== Building the binary and the source package ==
To build only binary package/s
<pre>
$dpkg-buildpackage -rfakeroot -b
</pre>
we can install these binary package with dpkg:
<pre>
$dpkg -i myapp.deb
</pre>

To build the source package and to sign it with your gpg key (ABCDEF12)
<pre>
dpkg-buildpackage -rfakeroot -sa -S -kABCDEF12
</pre>
At this point, if you have tested your package and it works fine you can [http://wiki.maemo.org/Uploading_to_Extras upload it in extras/extras-devel].

= Example =
You can download the source package of qt-maemo-example from the extras-devel repository just running if you have source packages enabled in your sources file;

''apt-get source qt-maemo-example''

This command will download the:

- unmodified source (.orig.tar.gz)

- debian dsc file (.dsc)

- diff file (.diff)

and after it will launch automatically dpkg -x file.dsc in order to uncompress the orig.tar.gz and apply the changes.

= Useful Links =
[http://qt4.garage.maemo.org Qt4Maemo at garage]

[http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-0.9.4.html Desktop entry spec 0.9.4]

= Debhelper 7 =
Debhelper 7 is not available in fremantle.
Debian packages that requires level 7 needs some changes:
eg:
* debian/compat: 7 -> 5
* debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5)
* And maybe comment out a few dh_* calls from debian/rules, which might not exist on level 5

Now things might get complex if the packaging already uses some new
features of level 7, like those CDBS-like helper rules. In such cases,
looking at versions prior to the compatibility level upgrade might
help doing the downgrade (and most Debian packages are kept in public
SCMs like svn.debian.org).

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

Packaging a Qt application

2010-01-15T21:16:58Z

88.115.28.145:

= Packaging a Qt application for Maemo=
== Finding your package in debian ==
If you want to port a Qt package to Maemo, you should check and see if it is already packaged for debian and use that package if you can - this will save you time and effort. You can search in debian's [http://www.debian.org/distrib/packages Package Tracking System (PTS)] to see if it is there. There is a search system on the PTS page, under the "distribution" drop-down, select 'any', this will search throughout debian's repositories to find the package. Debian has more than 20,000 packages just in its stable distribution so your application is likely already packaged.

If you find the package already exists in debian, you can get the source, including the packaging source, with apt-get. To do this, you'll have to edit your /etc/apt/sources.list, you can follow this recipe;

<pre>
$ echo “deb http://ftp.it.debian.org/debian/ unstable main contrib non-free” >> /etc/apt/source.list
$ apt-get update
$ apt-cache search "application name"
$ apt-get source "application name"
</pre>

''To learn more about the /etc/apt/sources.list you can do a 'man sources.list' if you are running debian or a debian based GNU/Linux distro.''

== Porting the debian package to a Maemo package ==
If your application has been already packaged for debian, you can begin your maemo packaging with this section. Once you have the source of the debian package, you will need to make some modifications to that package for it to build under Maemo. For the complete Maemo Package Policy, use [http://maemo.org/forrest-images/pdf/maemo-policy.pdf this link] to a pdf.

In order to create a new package for maemo, you'll need to:
* Rename the upstream source directory in Package-Version (eg: myapp-0.1)
* Create “src” directory in Package-Version/
* Copy all the files in the src/
* Rename src/appname.pro in src/src.pro
<pre>
$mv myapp myapp-0.1
$cd myapp-0.1
$mkdir src
$cp * src
$mv src/appname.pro src/src.pro
</pre>

Append the following chunk to end of your src/src.pro . The chunk adds install section to your qmakefile

<pre>
unix {
#VARIABLES
isEmpty(PREFIX) {
PREFIX = /usr/local
}
BINDIR = $$PREFIX/bin
DATADIR =$$PREFIX/share

DEFINES += DATADIR=\"$$DATADIR\" PKGDATADIR=\"$$PKGDATADIR\"

#MAKE INSTALL

INSTALLS += target desktop iconxpm icon26 icon40 icon64

target.path =$$BINDIR

desktop.path = $$DATADIR/applications/hildon
desktop.files += $${TARGET}.desktop

iconxpm.path = $$DATADIR/pixmap
iconxpm.files += ../data/maemo/$${TARGET}.xpm

icon26.path = $$DATADIR/icons/hicolor/26x26/apps
icon26.files += ../data/26x26/$${TARGET}.png

icon40.path = $$DATADIR/icons/hicolor/40x40/apps
icon40.files += ../data/40x40/$${TARGET}.png

icon64.path = $$DATADIR/icons/hicolor/64x64/apps
icon64.files += ../data/64x64/$${TARGET}.png
}
</pre>

*Create a myapp-0.1/myapp.pro file like this:
<pre>
QMAKEVERSION = $$[QMAKE_VERSION]
ISQT4 = $$find(QMAKEVERSION, ^[2-9])
isEmpty( ISQT4 ) {
error("Use the qmake include with Qt4.4 or greater, on Debian that is qmake-qt4");
}

TEMPLATE = subdirs
SUBDIRS = src
</pre>
*Run dh_make to debianize the source archive, it creates:
**An archive with the unchanged upstream source (orig.tar.gz)
**Some basic files in the debian directory
**Some example files (*.EX *.ex)
<pre>
dh_make --createorig --single -e maintainer@email.org -c gpl
</pre>

== Having a look inside the debian/ dir ==
At this point the directory my-app contains
* the source directory ( src/ )
* the debian directory (debian/)

Inside the debian dir we have the files needed for the creation of the debian package
* Changelog - Application's change log
* Compat - Debian helper compatibly version
* Control - Describes the packages to be made
* Copyright - Copyright text
* Rules - A binary makefile containing the rules to build the package

== Maemo Packaging Policy ==
Maemo packages follow the Debian Policy, but there are some items where Maemo:
* Is more strict (it is an embedded distribution)
* Is more relaxed
**Only a target device (Nokia Internet Tablet)
**Only a specified UI (Hildon)
**Only one user.
*Differs from Debian because Maemo has different:
**Objectives
**Maintainers
**Infrastructure

==Editing the Control file ==
Basically it specifies for each package (source or binary) a name, some dependencies, a description etc...
For a Maemo package these fields are very important:
* [http://wiki.maemo.org/Task:Package_categories#Translations Section]: Only the packages in the user segment are showed by App Installer.
* Maintainer: This field MUST be changed if the upstream package is modified
* XB-Maemo-Icon26: It contains the PNG icon encoded in base64 visible in the Application Installer

If you need to encode your icon as base64, there are [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package instructions here.]

<pre>
Source: my-application
Section: user/valid_subsection
Priority: optional
Maintainer: name surname <xxxxxxx.xxxxxx@maemo.org>
XSBC-Original-Maintainer: name surname <yyyyy.yyyyy@debian.org>
Build-Depends: debhelper (>= 5), libqt4-dev, OTHERS_BUILD DEPENDECIES
Standards-Version: 3.7.3

Package: my-application
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: A simple test application
A very simple application with a short description.
Which spans multiple lines actually.
XB-Maemo-Icon-26:
iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAYAAACpSkzOAAAABmJLR0QA/wD/AP+g
vaeTAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH1gURDQoYya0JlwAAAU9J
REFUSMftlL1KA0EUhb/NZl/ggnHQxsJUxt5CUucVJCCkDfgyKdIGG5/A0s5HEBtJ
EdDAQGBgmw0YJmMzgXXYza5CtNkDW9zZw5z7c+ZCgwb/Ai3i9sVl/Bq8RIs4LRK1
gJDsKvJyNXmJMuYTsMoY1zpgozaABdYArQNPZQ1kfyGU7SpqVwxzAMwABWhgpIwp
4vWBB+AUWAI3ypjnfEXtPU4bLKx9vErTeCeiRSYF+fTn1j5dp2myE9EiU+DSi3wX
ymeqRQAmZ3EcA5E/fgO6BULT8zhOcrwXoJdrXRa2Lgps2y2odAUcBUIXQdz78YyC
SldAp8b7+bXrIv91qjZBietqCc2DjbAt4b2WxJkyZljVujlwp0U0cPxuLcAIuC+4
dKxFlsDJarvdAGP/b6hFnDImYs+uG3hbO2AB3Jbsur63tQM+fFx3bzZocEB8AdV2
gJBZgKTwAAAAAElFTkSuQmCC

Description: A simple test application
A very simple application with a short description.
Which spans multiple lines actually.

Package: my-application-dbg
Section: devel
Architecture: any
Depends: my-application (= ${binary:Version})
Description: Debug symbols for a simple test application
Debug symbols for a very simple application, which allow
tracing and debugging.
</pre>

Valid subsections are:
* accessories
* communication
* games
* multimedia
* office
* other
* programming
* support
* themes
* tools

== Editing the rules file ==
The rules file generated by dh_make will be modified in order to look like this one.
We are using qmake, so we haven't a configure file to run.
If you cut-and-paste following file, notify that empty space beginning of lines it TAB characters, it is not multiple space characters. If you cut-and-paste
the following chunk, you most propably get spaces instead tabs and the file does not wok

<pre>
#!/usr/bin/make -f
APPNAME := my_app_name
builddir:
mkdir -p builddir

builddir/Makefile: builddir
cd builddir && qmake-qt4 PREFIX=/usr ../$(APPNAME).pro

build: build-stamp

build-stamp: builddir/Makefile
dh_testdir
# Add here commands to compile the package.
cd builddir && $(MAKE)
touch $@

clean:
dh_testdir
dh_testroot
rm -f build-stamp
# Add here commands to clean up after the build process.
rm -rf builddir
dh_clean
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs

# Add here commands to install the package into debian/your_appname
cd builddir && $(MAKE) INSTALL_ROOT=$(CURDIR)/debian/$(APPNAME) install
# Build architecture-independent files here.
binary-indep: build install
# We have nothing to do by default.

# Build architecture-dependent files here.
binary-arch: build install
dh_testdir
dh_testroot
dh_installdocs
dh_installexamples
dh_installman
dh_link
dh_strip --dbg-package=my-application-dbg
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dh_gencontrol
dh_md5sums
dh_builddeb

binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install configure
</pre>

== Editing the Changelog file ==
It is the log of the changes for a specified application version. It's important file because it sets the binary/binaries and the source packages version and revision.
If an upstream package is re-packaged or modified for maemo, the Maemo revision string should be appended to the upstream revision.
So if in Debian the package name was something like "Myapp-0.4-2" in maemo this package will be called "Myapp-0.4-2maemo0".
The number after the "maemo" string is a progressive number.

== Application menu icon & position ==
The Maemo application menu detects automatically an app that provides a .desktop file in /usr/share/application/hildon . If you don't have desktop file, create one in the src directory.

<pre>
[Desktop Entry]
Encoding=UTF-8
Version=0.1
Type=Application
Name=myapp
Exec=/usr/bin/myapp
Icon=myapp
X-HildonDesk-ShowInToolbar=true
X-Osso-Type=application/x-executable
</pre>

Maemo menu structure is completely different from Debian:
* An unmodified Debian package installs the proper .desktop in /usr/share/applications
* Applications that use the debian menu are displayed in the extra menu

In order to show our application in the correct Maemo menu:
* debian/myapp.install moves the .desktop file and icons in the right directory
<pre>
src/*.desktop usr/share/applications/hildon
src/*.png usr/share/icons/hicolor/26x26/apps
</pre>

* debian/postinst should call maemo-select-menu-location utility to permit the user to choose the menu location. '''This works only in Diablo, it doesn't work in Fremantle.'''
<pre>
#!/bin/sh
maemo-select-menu-location myapp.desktop
</pre>

== Checking Maemo Packages ==
Lintian dissects Debian packages and reports bugs and policy violations.
It contains automated checks for many aspects of Debian policy as well as some checks for common errors.
Unfortunately it doesn't check conformance to the additional Maemo policy.

Currently Maemo is creating [http://maemian.garage.maemo.org/ Maemian] to check its policy.

== Building the binary and the source package ==
To build only binary package/s
<pre>
$dpkg-buildpackage -rfakeroot -b
</pre>
we can install these binary package with dpkg:
<pre>
$dpkg -i myapp.deb
</pre>

To build the source package and to sign it with your gpg key (ABCDEF12)
<pre>
dpkg-buildpackage -rfakeroot -sa -S -kABCDEF12
</pre>
At this point, if you have tested your package and it works fine you can [http://wiki.maemo.org/Uploading_to_Extras upload it in extras/extras-devel].

= Example =
You can download the source package of qt-maemo-example from the extras-devel repository just running if you have source packages enabled in your sources file;

''apt-get source qt-maemo-example''

This command will download the:

- unmodified source (.orig.tar.gz)

- debian dsc file (.dsc)

- diff file (.diff)

and after it will launch automatically dpkg -x file.dsc in order to uncompress the orig.tar.gz and apply the changes.

= Useful Links =
[http://qt4.garage.maemo.org Qt4Maemo at garage]

[http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-0.9.4.html Desktop entry spec 0.9.4]

= Debhelper 7 =
Debhelper 7 is not available in fremantle.
Debian packages that requires level 7 needs some changes:
eg:
* debian/compat: 7 -> 5
* debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5)
* And maybe comment out a few dh_* calls from debian/rules, which might not exist on level 5

Now things might get complex if the packaging already uses some new
features of level 7, like those CDBS-like helper rules. In such cases,
looking at versions prior to the compatibility level upgrade might
help doing the downgrade (and most Debian packages are kept in public
SCMs like svn.debian.org).

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