Re: How do you build "against" the 10.3.9 sdk?
Re: How do you build "against" the 10.3.9 sdk?
- Subject: Re: How do you build "against" the 10.3.9 sdk?
- From: Mark Wagner <email@hidden>
- Date: Mon, 13 Aug 2012 14:20:17 -0700
On Mon, Aug 13, 2012 at 12:31 PM, Stephen Kay <email@hidden> wrote:
> (Using XCode 2.4.1 on 10.4.11 to port an old CodeWarrior project)
>
> In my Project's Inspector/General tab, I set the Cross-Develop Using Target
> SDK to "Mac OS X 10.3.9", but in the project, all of the included frameworks
> are still pointing at the current system (/System/Library/FrameWorks).
>
> Is this correct or am I missing some other step?
I think this is correct: Xcode will substitute the proper SDK paths at
build time.
> Secondly, my understanding is that it's only necessary to build against the
> 10.3.9 sdk in order to allow the app to run on 10.3.9; if I want to just say
> at this point "10.3.9 is no longer supported, 10.4 and higher", then I can
> just compile against the 10.4 (Universal) sdk (or the Current Mac OS on this
> 10.4.11 machine)?
In theory, the SDK you pick determines the newest API you can use, the
"minimum MacOS version supported" you specify determines the oldest
system you can run on, and any functions in the SDK but not the
minimum MacOS version will be weak-linked. So, in theory, you could
specify the 10.8 SDK and a minimum version of 10.3, use functions
present in 10.5 and newer, and so long as you check at runtime for the
existence of those functions and provide a workaround if they're
absent, everything will work.
In practice, it doesn't work so well, generally because of changing
library versions. I'm fairly sure that 10.4 SDK/10.3 minimum version
is one of the combinations that works, but you'll need to test it to
be sure.
--
Mark Wagner
_______________________________________________
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