I'm not sure if the old modifications will be of any use until we got the basic stuff running, because of the new QPA.
Btw: I found one error: libXlib-xcb* is needed but not available in the SDK. Luckily the old source package contains it.

*EGLDisplay needs a native display, which can't be accessed using XCB alone.

QtQuick2 works, but keyboard input does not work yet (not related to QtQuick, does not fork with widgets either).
Edit: Seems to be related to focus as keyborad works on some widgets.
Here is the new diff:
http://paste.kde.org/668450/04503991/
(password ist 1234(I thought, using a password would allow editing, which is not the case)).

You have to install libxcb-xlib0 (in the repos) on your device and build libx11 inside scratchbox. Add -with-xcb to the ./confiure call and copy include/X11/Xlib-xcb.h and src/.libs/libX11-xcb.so to e.g. qtbase/src/plugins/platforms/xcb and qtbase/lib/ respectively.
Better instructions will follow.

Edit2: Maybe I was a bit hasty, when I said we don't need the modifications yet, as http://qt.gitorious.net/+qt-develope...cation_x11.cpp contains xcb_atomnames missing in qxcbconnection.cpp and _HILDON_IM* sounds input related.

There are now two repositories on gitorious along with a user group: https://gitorious.org/+qt5-maemo5 . Anyone willing to participate should create a gitorious account and ask for inclusion here.

I've also created a wiki article: http://wiki.maemo.org/Qt5-Maemo5-Development


Is there any working debian repo where we could upload Qt5 packages and the aforementioned libX11-xcb*?

What do you think, is the correct repo in the long run: extras or cssu?

*I'm still not able to build the libx11-6 package in scratchbox (not even unmodified, i.e. using "-without-xcb" instead of "-with-xcb" in debian rules). I would greatly appreciate if someone could do that.

You can setup your own repo with reprepro: http://www.jejik.com/articles/2006/0...with_reprepro/

As a server, you might use hostinger.pl or 000webhost.com - I'm using 000webhost for my repo and it's ok for a repo.

Both can be used as qt5 will be parallel /edit: but extras will be considerably easier.

Maybe Qt5 build would be easier in Maemo SDK (Scratchbox)? No calls to Madde 4.6.2, and Maemo Qt is now 4.7 (no idea whether it uses Qt4)
Plus extras-devel tools

Ah sorry for that 4.6.2, that should be part of MADDEROOT (Edit: changed in the wiki). QtSDK still used that path even though it ships Qt 4.7, but that doesn,t matter since we don't need anything from Qt4.

No, I think Madde is better because a) it's a normal cross compile toolchain (like that one for the Pi or Android; keep in mind that Qt builds host binaries (moc, qmake etc. too)), b) it's the way it's done for N9 in the Qt-Project wiki, c) I failed to set it up in scratchbox, d) I'd like to have a Madde for Qt5 in the end.

You can try using scratchbox (as rzr did) and add a guide to the wiki if you like, if the autobuilder is up again this might be useful, however preparing packages for the autobuilder using Madde worked fine in the past (only minor changes are needed).

Btw:I've set up a debian repo, see the wiki page (http://wiki.maemo.org/Qt5-Maemo5-Dev...t5_on_the_N900). I have 100GB traffic per month, if it gets near a third or something like that, I'll have to move it.

You were right, I added these lines:
https://qt.gitorious.org/+qt-develop...1.cpp#line3231
(adapted to the QPA-plugin) to this place https://qt.gitorious.org/+qt5-maemo5...w.cpp#line1392

... and now the keyboard input works. I have to clean up a bit and recompile, before I commit them.
Edit: done.

Well done,

About libX11-xcb: you might use maemo-optify if you don't care about the location it's optified to. It's really easy

waiting for your release
thank you

@Alecsandru: Keyboard support is now in the debian repo, too. Be aware, that there are still some bugs. The ugliest thing I'm facing now, is a QtQuick2 bug, where every text is destroyed, if you set any text to a new value:

E.g. in the mousearea example everything is fine until you click on "Click". This sets 3 texts, but not "Click" and "Drag". Nevertheless every text including "Click" and "Drag" is completely unreadable afterwards (looks like random noise).

On the other hand my pdf reader flatboat (also in the examples folder of my repo, see Wiki) looks nearly like it did with Qt4. The text bug doesn't matter there, because every text is set only once.

@everybody: Do you thing porting the special Maemo5 widgets to Qt5 is important? I'm asking because this will take a lot of time and is probably even harder than creating new similar widgets, because they absolutely break the platform abstraction (they call X11 and Gtk stuff directly).

Nearly the same holds for the integration of the QMenuBar into the window's titlebar. I would change that to a simple signal (emitted, when you click on the titlebar), which allows for more flexible approaches (can be handled within QML). Of course, we also need a property which sets whether the little arrow on the title bar is shown.