[KDE/Mac] Creating a OS X packaging receipt for DMGs?

[Milian Wolff]

On Mittwoch, 9. März 2016 12:56:31 CET René J.V. Bertin wrote:
> On Wednesday March 09 2016 12:41:37 René J.V. Bertin wrote:
> 
> (too fast again)
> 
> > What I'm trying to figure out is the minimum subset of a full LLVM+Clang
> > install that will allow to build and run KDevelop (and possibly other
> > applications that use libclang).

Note again: We do not depend on LLVM or Clang in KDevelop. We only require 
libclang, the C API of clang, and yes - that is something different!

> What I'd also like to figure out is whether it's really impossible to use
> the Clang version bundled in Xcode. Apple doesn't include an llvm-config
> script, but it should be possible to work around that if nothing else is
> missing that is required.

Have you tried linking against that libclang? Is XCode also shipping the 
development headers? On Linux they are in /usr/include/clang-c, look for 
Index.h. I'm also interested in the values of the `CINDEX_VERSION_*` macros 
included therein.

> There should be no drawbacks to such an approach if the library can be
> embedded (nor for people who build against shared resources like I do).

This is contradictory, or I'm not following your train of thought. The above 
makes me believe you want to link against XCode's libclang, i.e. explicitly 
_not_ embed the library with KDevelop?

> If
> that's not doable you'd be looking at providing builds for the various
> supported Xcode versions, but you'd still get the advantage (on the build
> host) of not having to install and maintain an additional Clang install
> next to the one you're already obliged to install.

The Clang library has a C API with stable ABI. Thus linking against the 
minimum supported XCode that fulfills our requirements should be enough. Any 
later versions should then work as well. I.e. there is no need to support 
builds for various XCode versions.

> And Apple's clang builds
> are up to 50% faster than any other build I've been able to test (on OS X).
> I have no idea whether that applies to just the parser too, but it
> certainly shouldn't hurt.

That sounds like you did not disable assertions while building Clang.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- 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/20160309/d19de433/attachment.sig>