[cfe-dev] Using libc++ in a published app

[Nico Weber]

clang now depends on libc++, but we still need to run clang on 10.6
machines in chromium land. What we do is link libcxx and libcxxabi into a
dylib (linked with -install_name @executable_path/libc++.dylib) that we put
right next to the clang binary that's shipped to bots and developers. The
binary appears to work on all OS X versions from 10.6 to 10.9. I'm not sure
if doing this is a great idea, though :-)

(See
http://src.chromium.org/viewvc/chrome/trunk/src/tools/clang/scripts/update.sharound
line 380 for details, and newer binaries at
http://commondatastorage.googleapis.com/chromium-browser-clang/index.html?path=Mac/for
how it looks in compiled form.)

Nico


On Sun, May 11, 2014 at 10:16 PM, Sean Colombo <sean.colombo at gmail.com>wrote:

> Hi there,
> When releasing an OSX app using libc++, is there any standard way to make
> sure the user has this dependency installed?
>
> It appears that users on OSX 10.6 and below do not have libc++ by default
> (that's around 20% of OS X users at the moment).
>
> If I simply package libc++.1.dylib with my app, I assume it will continue
> to fail because there seems to be a large number of cascading dependencies.
>  Is there some script I could run at installation-time to make sure libc++
> and all of its dependencies get installed?
>
> Thanks for any pointers you could give me!
>  - Sean Colombo
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140513/8f59e1e5/attachment.html>