Re: Base SDK vs. Deployment SDK
Re: Base SDK vs. Deployment SDK
- Subject: Re: Base SDK vs. Deployment SDK
- From: Matt Neuburg <email@hidden>
- Date: Tue, 29 Jun 2010 07:34:44 -0700
- Thread-topic: Base SDK vs. Deployment SDK
On Mon, 28 Jun 2010 23:44:51 -0400, Laurent Daudelin
<email@hidden> said:
>On Jun 28, 2010, at 14:37, Christiaan Hofman wrote:
>> One confusion you seem to have is that there's no thing like a "deployment
SDK". I assume you mean "deployment target", which has nothing to do with any
SDK.
Yeah, I just mistyped the name myself in a different thread on this same
list on this same topic. It's easy to do in the heat of the moment. But, you
mean what I know.
>>> If I create a new project for iPhone and want it to be compatible with
3.1.3, I know that the deployment SDK should be that version but what about the
base SDK? Setting it to 4.0, am I not going to miss warnings if I use methods or
classes that were introduced in 4.0 but are not available in 3.1.3?
Yes. See my post in the other thread. :)
>The problem I just realized, at least for the iPhone, is that the oldest SDK
that I can use as a base is 3.2, no 3.1 anymore. I wish 3.1 or 3.0 could still
be an optional install, like 10.4 is for Mac OS X...
The removal of the multiple specific base SDKs in the move from Xcode 3.2.2
to Xcode 3.2.3 is certainly a surprise. It isn't so much the removal of the
different SDKs from the Overview pop-up menu / Build menu, since they should
probably not have been there to start with and may have been confusing to
some. It's the fact that you can no longer install e.g. the iPhone OS 3.1.3
SDK at all (and so you can't set the Base SDK to it).
(I have a suspicion that this may have been necessary in order to implement
the very flexible new Simulator. Not so long ago, Fritz Anderson was
complaining that the Simulator didn't use the "modern runtime" and so would
choke on code like synthesized ivars that would work find on the device
itself. Well, now the Simulator *does* use the "modern runtime". I'm
guessing that this just wasn't do-able with older Simulator that could run
3.1.3 and before. But that's just a hunch without any evidence.)
The solution, of a sort, is that you can have more than one Xcode installed.
So, reinstall Xcode 3.2.2 with its multiple base SDKs, side by side with
Xcode 3.2.3. Now you can develop on 3.2.3 with iOS 4.0 as a base SDK, but
every once in a while you open the project in Xcode 3.2.2 with a lower base
SDK and see what happens.
m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings
_______________________________________________
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