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

List:       kde-devel
Subject:    Re: kde and clang
From:       Ian Wadham <iandw.au () gmail ! com>
Date:       2013-02-19 12:09:42
Message-ID: 55029E7D-2582-4F58-8A4B-329B6C23B709 () gmail ! com
[Download RAW message or body]

Hi Agostino,

On 19/02/2013, at 7:59 AM, Agostino Sarubbo wrote:
> I don't know if someone in the past have checked if the kde metapackage is 
> "compatible" with clang. I just compiled the entire kde-meta-4.9.5 right now 
> and all packages was fine.

The Macports group have been using Clang for about a year as their default
compiler for porting FOSS into recent versions of Apple OS X.  That includes
all released KDE software and Qt4-Mac.  I am a KDE Games developer
working on an Apple Macbook Pro and I have been using Clang for all
my development work since about May/June last year.

There is one fairly big problem and that is that the macro-generators behind
KDE builds are not Clang-ready --- mainly that KDE_EXPORT and friends
are not Clang-ready.  This caused me a lot of grief for a while, see:

    https://bugs.kde.org/show_bug.cgi?id=300429

You may find the later comments by a KDE build-team guy interesting.

Apart from that problem, I have found a couple of bits of legacy source code
in KDE Games that caused compiler errors in Clang, but compiled OK for
years in GCC.  They were easily fixed, but it appears that Clang is a bit more
rigorous than GCC when compiling C++.

Clang works fine for me now and, as a developer, I like it better than GCC
because it gives clearer diagnostics messages on souce-code errors.

Cheers, Ian W.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]