building with llvm/clang 3.5?

[Kevin Funk]

On Saturday, March 12, 2016 2:56:35 PM CET René J.V. Bertin wrote:
> Hi,
> 
> Does anyone know if KDevPlatform and KDevelop are still supposed to build
> with clang 3.5 (specifically Apple's clang-600.0.57)?

Clang 3.5 is still supported (it's the minimum version). It is used on build.kde.org (KDE CI). But as 
always: We do not know how much Apple patched their Clang fork, so it might be difficult to rely 
on it (but we already discussed that in an other thread).

> I'm getting
> symbol-not-found link errors (e.g. with CMakeBuildDirChooser functions)
> that appear to be due to visibility handling, and that disappear when I
> build with clang >= 3.7.0 .

I'm not sure how CMakeBuildDirChooser is related to Clang...?

Please post the compile error.

Cheers,
Kevin
 
> Curiously I've been able to do an incremental build of the same (KDevelop)
> commit that now fails to build, probably because the problematic files
> didn't require rebuilding (or cmakecommonexport.h wasn't re-generated)?!
> 
> Depressingly, it took me half a day before I decided to try a more recent
> compiler, as a last resort :-/
> 
> R.
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel


-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160312/c5255426/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160312/c5255426/attachment.sig>