[cfe-dev] Making libc++ on Linux user-friendly

[David Chisnall]

On 31 Mar 2014, at 17:45, Hal Finkel <hfinkel at anl.gov> wrote:

> ----- Original Message -----
>> From: "David Chisnall" <David.Chisnall at cl.cam.ac.uk>
>> To: "Sebastian Redl" <sebastian.redl at getdesigned.at>
>> Cc: cfe-dev at cs.uiuc.edu
>> Sent: Monday, March 31, 2014 10:55:09 AM
>> Subject: Re: [cfe-dev] Making libc++ on Linux user-friendly
>> 
>> On 31 Mar 2014, at 16:27, Sebastian Redl
>> <sebastian.redl at getdesigned.at> wrote:
>> 
>>> The other problem is this: how do we make it so that no additional
>>> command line flags are required, no matter what ABI library is
>>> used? Ideally, the libc++.so would just tell the linker to pull
>>> the ABI library into the link, or claim to export the symbols
>>> itself but really just forward to the underlying library.
>> 
>> This is what we do on FreeBSD:
>> 
>> $ cat /usr/lib/libc++.so
>> /* $FreeBSD: release/10.0.0/lib/libc++/libc++.ldscript 253917
>> 2013-08-03 16:23:43Z dim $ */
>> GROUP ( /usr/lib/libc++.so.1 /usr/lib/libcxxrt.so )
> 
> Can this work for static libraries also?

The problem doesn't arise for static libraries - you just link the libcxxrt / libsupc++ .o files into libc++.a when you link it.  Our libc++.a contains libcxxrt. 

David