Re: old c++ std includes
Re: old c++ std includes
- Subject: Re: old c++ std includes
- From: Chris Espinosa <email@hidden>
- Date: Thu, 18 Sep 2008 13:37:37 -0700
On Sep 18, 2008, at 11:17 AM, John Robinson wrote: Why does the XCode 3.1.x install not upgrade the /usr/include/c++ directory with the 4.2.1 includes?
There are several bugs and missing features in gcc 4.0.0 (especially regarding TR1) that have been fixed in newer gcc releases, yet, despite switching to the 4.2.1 gcc compiler in XCode, we are unable to take full advantage of them.
I've heard that it's possible to switch to a manual install of the gcc compiler. If so, is that the recommended (or even only) way to obtain 4.2 std includes on OS X and how would one go about modifying XCode to use such an install? Is it via the GCC_VERSION setting? We've not yet integrated the 4.2 Standard C Libraries with Xcode because no shipping operating system has them installed on the user side. As most Mac OS X apps link dynamically against the libraries installed in the OS, rather than carrying their own copy with them, shipping 4.2 libraries in Xcode would have little value until the 4.2 libraries are deployed in a copy of Mac OS X.
When a new version of Mac OS X bundles the 4.2 libraries, then you'll be able to build applications using gcc 4.2 in Xcode that link against those libraries and deploy them, but there is a possibility that you will need to require users to upgrade to that version of the OS to get functionality or bug fixes exclusive to the 4.2 libraries.
You can always build your own static version of the 4.2 libraries and link to them, but you'll need to convince gcc not to use its own version of the headers using -nostdinc.
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden