Re: Unavailable Function Errors and Backwards Compatability
Re: Unavailable Function Errors and Backwards Compatability
- Subject: Re: Unavailable Function Errors and Backwards Compatability
- From: David Alger <email@hidden>
- Date: Wed, 14 Mar 2007 20:11:47 -0500
On Mar 14, 2007, at 6:43 PM, Laurence Harris wrote:
On Mar 14, 2007, at 12:31 PM, Sean McBride wrote:
On 3/13/07 9:32 PM, David Alger said:
I have looked all over for this, but can't seem to find a way. I want Xcode to emit an error when I try using functions that are not available in 10.3.9 and earlier while at the same time compiling against the 10.4u SDK. Is there a way to do this.
I have tried setting these defines...
#define MAC_OS_X_VERSION_MIN_REQUIRED MAC_OS_X_VERSION_10_3 #define MAC_OS_X_VERSION_MAX_ALLOWED MAC_OS_X_VERSION_10_3
You are not supposed to #define these in your code. This has been discussed many times in the past, see for example:
True, but he said he'd tried setting those defines, so I was just wondering why he hadn't used 10.4.
Read last Post.
David, what is your deployment target set to?
I've set it to 10.3 and 10.4, it doesn't seem to make a difference with this.
David
<><><><><><><><><><><><><><><><><><><><><><> <>Why are C string processing functions so ruthless? <> <>Nothing at stop they because :rewsnA <><><><><><><><><><><><><><><><><><><><><><><>
|
_______________________________________________
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