Re: building for 10.5 vs 10.6
Re: building for 10.5 vs 10.6
- Subject: Re: building for 10.5 vs 10.6
- From: Christiaan Hofman <email@hidden>
- Date: Mon, 28 Jun 2010 20:12:49 +0200
On Jun 28, 2010, at 19:59, Bill Appleton wrote:
> hi all,
>
> i am currently building for 10.5 because that is our minimum user requirement
>
> there are some 10.6 functions i want to use, so i just check at runtime and use 10.6 if available
>
> but i am targeting 10.5, so i get an xcode warning in these places, "NSWindow may not recognize etc"
>
> so should i just target 10.6? or does that make internal libraries or frameworks (etc) not work on a 10.5 machine?
>
> maybe the danger is that i will accidentally use a 10.6 fx elsewhere without the runtime check
>
> is there a way just to suppress the warning? what do you guys do about this issue?
>
>
> thx
>
> bill
The normal way to do this is to use the 10.6 SDK and set the deployment target to 10.5. This allows you to use 10.6 API, and when properly checking should allow your code to run on 10.5. It won't warn you about the use of 10.6 API though, but you must check for it, usually by checking for the availability of the particular API rather than the OS version (for a method use -respondsToSelector: or -instancesRespondToSelector: and for a function check whether the address is non-NULL). If you want to see warnings for API not available on 10.5 you may want to regularly compile your code using the 10.5 SDK (hold down Option and select from the build style popup, or Project > Set Active SDK).
Christiaan
_______________________________________________
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