[KDE/Mac] Repository for patches to fix KDE Problems on OS X

"Marko Käning" mk-lists at email.de
Sat Jun 28 13:03:15 UTC 2014

Hi Ian,
> Heh, heh! I can claim to have played a small part in that:
> https://bugs.kde.org/show_bug.cgi?id=300429#c19
> Also this little thread is an object lesson in what can happen with Clang:
> http://lists.kde.org/?l=kde-games-devel&m=139632085823089&w=2[http://lists.kde.org/?l=kde-games-devel&m=139632085823089&w=2]

I remember those two. :)

> I have seen only one or two real errors in legacy games code that Clang picked
> up. They have long since been fixed and were pretty harmless anyway, but library
> code can be more complex, so keep your eyes peeled…

Well, you are probably right: most of the stuff I found where rather "coding-style-related".

> > All you need is to get Qt4 installed. (I guess we can simply use qt4-mac!)
> From current MacPorts? Indeed you can! And I do.

That would be great if it worked, but you see: for the Qt5/KF5-KDE/CI system I was
required to build Qt5 from source! We'd need to figure out whether Qt4 from MacPorts
would be good enough for the CI system.

> It is not hard. A very small number of environment variables can be used to point
> everything at qt4-mac. The main one is QTDIR=/opt/local, or wherever. That's how
> KDE guys in general moved between Qt3 and Qt4.

Well, we'll see then how it works out. I'll try to set up a qt4-mac installation with the
KDE/CI system scripts in place and an adapted configuration then.

> Well, as much as I can. Don't forget I am a Venerable KDE Programmer [1].

Thanks, Ian!

> One cannot keep assimilating new stuff at the same rate forever. VMs and
> CI systems have both passed me by. I stumble a lot even with git.

I stumble a lot over git myself, since I am so used to Mercurial since years. ;)


More information about the kde-mac mailing list