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

[Milian Wolff]

On Mittwoch, 9. März 2016 12:41:37 CET René J.V. Bertin wrote:
> On Wednesday March 09 2016 11:10:03 Milian Wolff wrote:
> > > The question stands what is needed to build that parser. I'm guessing
> > > KDevelop isn't the only tool that can leverage libclang without
> > > requiring a
> > > full LLVM+CLang install.
> > 
> > What parser are you talking about?
> 
> The C/C++ parser. Does KDevelop use libclang for more than one parser?
> 
> > > Not even for building the parser?
> > > Being able to use an existing, external clang install would still be
> > > preferable in my opinion but I have no idea if that would even have been
> > > possible.
> > 
> > What parser again? Do you mean the code that uses libclang?
> 
> Yes, any parser or other code that uses libclang.
> 
> > You can build that
> > with any somewhat recent C++11 compiler, no need to build it against the
> > Clang that corresponds to the libclang we use. They are unrelated.
> 
> Well, yes. It's also evident that libclang will depend on at least libLLVM
> (mine does, at least; the one inside Xcode has no LLVM dependencies
> apparently).

This happens when you build enable shared libraries for libLLVM. This is not 
good for performance, and should not be done when you want to create a 
libclang for redistribution purposes. See also Kevin's mail, where he shows 
the small size of a statically linked libclang.so on Windows. Note: Libclang 
itself is still a shared library!

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/1475f86b/attachment.sig>