As most of you are probably well aware, since quite a while it is not very hard to write Qt applications to run on Android devices. A couple of weeks ago we at KO GmbH decided to look into how hard it would be to get KDE applications to run, and more specifically, if it would be possible to run Calligra with one of its mobile UI's on an android device.

I finally got around to running vttest [1] in Konsole (4.8/master) [2].

The most noticeable issue is the the console resizing commands don't work [3].

First, I've changed the branches that are being built on build.kde.org to reflect the branching of 4.8.

Second I've incorporated a build of Qt 4.8 branch that is triggered once a week to keep up with fixes there.

Third I've tried to get a build of Qt 5 up and running also, however this is where I've hit some bumps. I've been unable to get Qt 5 to build and as such not all other jobs are working :(

kdelibs frameworks branch is now covered in build.kde.org :)

But due to a bug in the build system it requires a special hack to build, ie the cmake call does all the required work but fails with a message about inqt5 not being in the export set. So to make it build in Jenkins the exit code from cmake has to be ignored. Other then that it seems to work ok.

A long over due update on the status of build.kde.org.

It now builds most of the old core KDE modules. Both the stable, currently the KDE/4.7 branch and the master branch. Sadly I haven't gotten Qt5 or kdelibs frameworks branch to build as a result nepomuk-core doesn't build either.

There is also an IRC channel for notifications on the build status, #kde-builds.

A second build node has been added that kicks in when the master node is busy, as this node is low on bandwidth it is set to only try and build if the master has been busy for some time.

Current list of jobs:

As Andreas note we are rather close towards Calligra 2.4 which will be the very first release of the Calligra Suite.

Our pretty cool Calligra Quality Dashboard lists 11 remaining release-critical blocker bugs that still need to be fixed till then.

There's been a "small" upgrade to my desktop machine at work, and as a part of that I got my hands on a 1920x1080 Dell monitor and couldn't help placing it as a secondary monitor, rotated. And I couldn't help noticing various problems with this setup.

Today is the second and last day of the Calligra Words mini-sprint. After spending yesterdays first day on planing and implementation of decisions made we spent today on solving all kind of problems that showed up since then.

In particular today we land;
* Fix wrong placement of anchored object if the object is anchored in a paragraph that spans two pages, and the anchor is in the part of the paragraph that is on the first page.
* Be sure to only try position an anchor once per layout-run.
* Implement anchor stacking.

Actually it's day #2 already since Boemann and myself already started hacking away yesterday evening when I arrived at his place in Denmark.

The main goal of our small mini-sprint is to address the various problems we have within Calligra Words with anchors and anchoring objects and text running around such anchored objects.

Thanks to our fabulous sysadmin team KDE now has a Jenkins installation[1] that serves kdelibs (KDE/4.7), kde-runtime and kdepim* (all master).

The plan is to have this as a pilot and if that goes well expand to include all (main) modules, stable and master branches.

[1] http://build.kde.org