2/ or in the sdk repo

Now there is a tar'ed toolchain to install in scratchbox (also build in scratchbox).

Removed the outdated instructions, see http://wiki.maemo.org/Qt5-Maemo5.

Please try to build some examples (e.g. from https://qt.gitorious.org/+qt5-maemo5...aemo5/examples) and/or your favorite Qt5/Qt4 program, run them on the device and report the results in the wiki: Qt5-Maemo5/WhatWorks.

Some notes:

• requires linaro-gcc.4.7 (http://wiki.maemo.org/CSSU-thumb_too...cc4.7.2-linaro) and thumb2-support on the device (i.e. power kernel >= 51 or cssu-kernel), the installation of the entire cssu-thumb repo should not be required
• be aware of the Text rendering bug in QtQuick2, so use TextWA instead of Text for simple labels if they are unreadable (only supports text, color and font.* attributes and everything inherited from Item)
• the Maemo5 Widgets and the style are not ported to Qt5 and probably never will, because the platform abstraction nearly requires a rewrite of those
• to test them on the device do the same as in scratchbox, but remove the directories: include, doc, mkspecs, bin (you may want to keep some tools in bin)
• qmake is build as arm binary, so it has to be emulated on the host and may not be very fast (no harm if you only have a single or few .pro files)

Little Update:

1. QtMultimedia is tar'ed now:
   http://repos.fuhlbrueck.net/qt5-maem...-maemo1.tar.gz
   and successfully tested with Ubuntu's joke example (see wiki)
2. QtDeclarative TextWA element no longer causes segfaults if color is set (and default color is black not red): http://repos.fuhlbrueck.net/qt5-maem...-maemo2.tar.gz
3. Started a qt-poject.org thread thread for the Text item bug.

Big update:

1. new wiki hierarchy, see http://wiki.maemo.org/Qt5-Maemo5
2. debs are available in the repo (see wiki), no need to unpack tars any more
3. all builds are performed from within scratchbox, so you can use Qt5 in the same way as Qt4 from scratchbox
4. QtMaemo5 module and QMaemo5Style (now part of the module) ported to Qt5 (but Maemo5 style is not the default style!), so widget based Maemo5 Qt4 apps may be ported with fewer efforts
5. In the aforementioned qt-project thread someone mentioned a similar problem to the QtQuick Text item bug while debugging on Windows. The poster promised to provide some example soon.
6. My repo (see wiki) also contains some test apps. You may suggest more apps, but they either have to be Qt5 apps or you must send me the ported source code. Currently there's only a widget based desktop build of trojita (package name trojita-tp). Try it with different -style and -stylesheet options.
7. I'll not have much time during the next 2-4 month, so development will slow down.

Some details for the further interested:

Don't use QMaemo5Style directly as this now requires the private headers (e.g. QT += widgets-private in your .pro file). The package qt5-maemo5 contains a style plugin in the next version, so use QStyleFactory::create("maemo5") instead of QMaemo5Style();

Porting the required QGtkStyle (see repo) back to gtk 2.14 (vanilla Qt5 claims it would need 2.18) was a matter of replacing function calls with macro calls. The way Qt loads the library functions from Gtk2 is quite interesting: Qt requests pointers to functions and call those functions later, without checking for null pointers. So an old Gtk2 version causes no compile time errors and the application silently segfaults. Since most of the required gtk calls are present, simple example apps even worked before I backported to older gtk, because the null pointers were simply not called at all.

During some tests with qtquickcontrols I made an observation regarding the Text item bug, details: http://qt-project.org/forums/viewthread/30543/#136584 .

As qtquickcontrols uses the native widget style to render its elements, they really look maemish, if called with "-style maemo5". I've put additional examples on my server, see http://repos.fuhlbrueck.net/qt5-maem...quickcontrols/.
If we could get this a little faster, we would have a better integrated QML items then with Qt4 (it's hard to distinguish "text" from a QtWidget app).

The "text" and "gallery" examples are probably the most interesting ones. "touch" is 10 times faster (does not use native style, i.e. doesn't load gtk stuff on Maemo5), but suffers from the Text bug, while the button labels in "gallery" are rendered correctly.

Text item bug is gone: https://qt.gitorious.org/+qt5-maemo5...a1c9982de97b95
I had to disable an efficient cache, but maybe we may re-enable it after some investigation.

New qt5-declarative is already in the repo.

Do we have any updates on Qt5 progress?

I'll just add that if at least Qt 5.1 (has QtQuick Controls) or preferably Qt 5.2 (QtPositioning) is available, the new Qt 5 modRana GUI I am currently working on will be able to run on the N900.

@Android_808: Sorry, I have currently only very few time for programming stuff and some of that went into porting flatboat to Qt5 and mupdf 1.3. Qt5.2 for Maemo5 is still on my TODO list. However, it might be even easier to adapt than Qt5.1, since one of the blogposts mentioned they revised some of the core elements of QtQuick2.

@MartinK: Please see http://wiki.maemo.org/Qt5-Maemo5/WhatWorks . QtQuickControls is one of the modules that work (with some quirks IIRC).

@frafl: Maybe you could create a separate branch and merge Qt5.2. And somebody (maybe me if I find time) would build it.