Date: Mon, 17 Sep 2012 15:37:17 -0500 From: Brooks Davis <brooks@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: toolchain@FreeBSD.org Subject: Re: enabling libc++ by default when building with clang Message-ID: <20120917203717.GB43626@lor.one-eyed-alien.net> In-Reply-To: <505782D2.2030103@FreeBSD.org> References: <20120917191028.GA42648@lor.one-eyed-alien.net> <505782D2.2030103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2012 at 10:06:42PM +0200, Dimitry Andric wrote: > On 2012-09-17 21:10, Brooks Davis wrote: > > Now that we have the COMPILER_TYPE variable I'm following up on an idea > > by theraven@ that we should enable libc++ by default when we are > > building world with a compiler that supports it. The following patch > > implements this: > > > > http://people.freebsd.org/~brooks/patches/libc%2b%2b-default.diff > > > > One key question is, when do we want to throw this switch? Do we do it > > now so people using clang start using it sooner or do we wait until > > we've switched the default compiler and things have settled a bit? >=20 > Well, building libc++ does not mean automatically using it. What is the > use case for only building (and installing) libc++, but not linking it > to anything? Just so people could build something with it later on? For now it's really so that people can start testing it without having to tweak more switches. From that perspective it probably makes sense to throw the switch sooner so it's readily available for people who want to start testing it. > In any case, I have been building libc++ for a long time now, and also > did some commits left and right to be able to actually use it for the > base system, e.g. all C++ programs in my installations are already > linked to libc++ (dynamically or statically). I have seen no problems > at all, and I am even working on a WITHOUT_LIBSTDCPLUSPLUS option. :) >=20 > I think the end goal should be to enable building and using libc++ with > one switch. And sooner or later, to make that the default. Then > FreeBSD will finally be able to use C++0x and C++11 features natively. It seems to me that installed, but not used by default is a useful transition state since it reduces the number of knobs required to try it out. If it turns out that other people's experiences match yours then we'll be a in a good position to flip the default linkage switch as well. -- Brooks --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFQV4n8XY6L6fI4GtQRAqpOAKDl+HUUTzuN7Er0/aPRFty/TCQwZgCeM/d0 vt0/zybBdajdVZffxvJ66wM= =Ft9j -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120917203717.GB43626>