Date: Tue, 29 Oct 2013 00:16:17 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Michael Gmelin <freebsd@grem.de> Cc: "freebsd-ports@freebsd.org list" <freebsd-ports@freebsd.org> Subject: Re: Build C++ based packages using C++11 Message-ID: <CA2B36F5-2251-471B-A375-52A1582474ED@FreeBSD.org> In-Reply-To: <20131028195708.53325afe@bsd64.grem.de> References: <20131028195708.53325afe@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_E676660B-6C44-4478-9182-D04158F21451 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 28 Oct 2013, at 19:57, Michael Gmelin <freebsd@grem.de> wrote: > Now that most ports build ok with clang, are there any steps planned > towards supporting C++11 and libc++ in the ports tree? I'm thinking of > flags like NEEDS_CPP98, NEEDS_CPP11 etc. With C++14 at the horizon I > expect more problems with ports depending on C++11 and even though > mixing standard libraries and language revisions might build in many > cases, it can lead to terrible problems at run time. Aren't the Mozilla ports already doing something like this now? (See https://developer.mozilla.org/en-US/docs/Using_CXX_in_Mozilla_code for their specific needs.) -Dimitry --Apple-Mail=_E676660B-6C44-4478-9182-D04158F21451 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlJu8EgACgkQsF6jCi4glqP0tQCfQ5jWkTcRElabFfri5RYbEJIH M04Ani4O5dvREpAN3J6oX4Mf5DK/gHde =3icJ -----END PGP SIGNATURE----- --Apple-Mail=_E676660B-6C44-4478-9182-D04158F21451--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA2B36F5-2251-471B-A375-52A1582474ED>