On Wed, Dec 04, 2013 at 12:48:13PM +0100, Titus von Boxberg wrote: > libc++ is available since 10.7. clang is available from Apple way > before Xcode 5. > > It's just that the libc++ of 10.9 and clang of Xcode 5 are the first > versions by Apple that have had a chance to use the clang/libc++ that > has (or claims to have) full C++11 support (actually, I don't know if > that's really the case since I don't have 10.9/Xcode 5). > > When sticking to C++03 or at most the subset of C++11 that had already > been implemented when 10.7.x shipped (which most ports currently do, I > think), macports should work with libc++ on the three most recent OSX > versions.
But if we're not going to use the default C++ runtime on these older systems anyway, we could just port a recent version of libc++ with full C++11 support and use that on these systems? That would avoid the potential brokenness of some C++11 features in libc++ on <= 10.8. Or am I mistaken here? -- Clemens Lang _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
