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: Nick Zitzmann <email@hidden>
- Date: Mon, 13 Aug 2012 15:11:19 -0600
On Aug 13, 2012, at 1: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?
That is correct behavior. The SDK setting is just an option that is passed to the compilers and linker.
> 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)?
Using an SDK means that the code will be linked against a stub version of the libraries that came with that version of the OS, which means that if you try to use symbols that are only present in a newer version of the OS, you'll get either build warnings or errors depending on the kind of code it's compiling and the build settings.
The deployment target setting matters more when targeting an older OS, since newer versions of the OS often use newer load commands that are unknown to older versions of the OS. If you don't push back the deployment target accordingly, you can get a binary that can't be loaded by older versions of the OS due to it containing load commands the old OS doesn't understand.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
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