[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-mac
Subject:    Re: [KDE/Mac] Repository for patches to fix KDE Problems on OS X
From:       <mk-lists () email ! de>
Date:       2014-06-27 7:00:55
Message-ID: DDC56358-9801-49E5-AFF1-68E93859D99A () email ! de
[Download RAW message or body]

Hi Ian,

On 27 Jun 2014, at 03:43 , Ian Wadham <iandw.au@gmail.com> wrote:
> Where have you been? :-)
on a long holiday with my younger daughter. :)

> Are we going to let Homebrew people have a look?  I don't see why not.
Well, they can have a look as we can have a look at their patches, right? :)

> Meanwhile, development of baloo, especially in the KF 5 version, is
> proceeding at supersonic speed.
Yep, Qt5/KF5 is why I was focusing on getting the KDE/CI system for
OSX/MacPorts to work in the last while=85

> However, as soon as anyone sets up a CI environment for KDE on Apple
> OS X, osx-patches and the existing patches MacPorts has for KDE will be
> suddenly in demand, I predict.  Otherwise, the CI will crash all over the
> landscape on day one.
=85 and last night I wanted to send an update to the list, but got stopped,
because I suddenly made a little more progress patching Qt5 itself to suit
the CI system=92s need regarding QStandardPaths.

Well, for now I might say this:

After having been in a almost exclusively bilateral discussion with Ben Coo=
ksley
I thought it would be good to update you all about the status of our effort=
s to
set up a MacPorts-based KDE/CI-system on OSX for Qt5/KF5:

 1) The KDE/CI system is eventually able to successfully build all framewor=
ks
    of tiers 1 to 4 relevant for OSX. (Not all frameworks have successfully
    running tests yet, though.)
    But, Ian, see we are far from your scenario where the KDE/CI system is =

    failing on OSX in all possible corners - instead we=92ve got the rather
    comfortable situation of overall successful builds and installs! :)

 2) I=92ve added a few bash scripts to [1] which ease the build/install of =
the
    various KF5 frameworks, which allow a relatively quick build of all
    frameworks despite quite a few failing tests which need some manual
    intervention.

For the jenkins build slave to work it is necessary that one can define sta=
ndard
search paths for application data (and probably also for the application bu=
ndle
directory). On Linux this can be achieved somehow, but on Windows as well as
here on OSX the Qt5 has some trouble in QStandardPaths! There has been some
discussion on kde-frameworks-devel [2] about it and this is where I progres=
sed
last night=85 :)

I have posted already on Qt-dev [3], but I don=92t expect response=85

Check out [4] if you want to learn more about the current status of the KDE=
/CI
system.

  Summarising - I am rather optimistic that we will get a full-blown
  jenkins build slave up and running on OSX in the nearer future!!!

Will proceed responding to your other post.

Greets,
Marko



[1] https://projects.kde.org/projects/playground/sdk/macports-kde/repositor=
y/revisions/master/show/contrib/scripts/KDECI
[2] http://mail.kde.org/pipermail/kde-frameworks-devel/2014-May/016059.html
[3] http://qt-project.org/forums/viewthread/44258/
[4] https://trac.macports.org/wiki/KDEProblems/KDEMacPortsCI/Status
_______________________________________________
kde-mac@kde.org
List Information: https://mail.kde.org/mailman/listinfo/kde-mac
KDE/Mac Information: http://community.kde.org/Mac
[prev in list] [next in list] [prev in thread] [next in thread]