Re: Developing for 10.4 and up
Re: Developing for 10.4 and up
- Subject: Re: Developing for 10.4 and up
- From: Alexander Bokovikov <email@hidden>
- Date: Sat, 16 Jan 2010 10:18:09 +0500
On 16.01.2010, at 4:40, Chris Espinosa wrote:
When you run on 10.5, you always get the 10.5 binaries no matter
what you linked against.
I'm sorry, but I'd say, "your binaries are those, whose API they use".
Framewoks are only linked, they're not a part of your binaries. Of
course, inner content of several versions of the same framework may
depends on its version even in the part, common (in the calling
interface) for many versions. But you can't choose, what exact
"version" of system frameworks to use, unless you'll include them
physically into your app bundle, what nobody does.
"...if you are doing a small incremental update of your application
to address a few bugs, it's usually best to continue building on the
same build environment and libraries used originally."
These words a worth of gold. Just because of inner peculiarities
between different versions of the same SDK.
So even if your app does not use 10.5 APIs, you might get different
behavior when building against the 10.4 SDK vs. the 10.5 SDK.
I'm sorry, but this statement is unclear for me. I always believed
that SDK are linked "dynamically", so the same binary could work on
several OS versions, having several SDK's. I'd say : "even if your app
does not use 10.5 APIs, you might get different behavior when you run
your app on 10.4 and 10.5 OS version". Of course, it's assumed, that
used SDK's are compatible with every version. For example, you've
built against 10.4. You may (or may not) get different behavior
running your app on 10.4, 10.5 and 10.6 OS.
As for me, for debug purposes I'm building my app against the lowest
SDK, I consider to support, say 10.4. This action reveals all possible
errors in code, where I've used improper methods. But there are some
cases, when we can see a recommendation in the doc to use another
method in the later SDK versions. in such case my app has a
conditional section, depending on base SDK (to escape from warnings).
Such section has a variant of code, oriented for the latest SDK, but
always including "respondsToSelector" preliminary check.
I'm building Release version against the latest SDK, corresponding to
my current OS. Then I'm testing my app on a lower OS version, but now
most of possible bugs are already fixed, so I can reveal only some
bugs, caused either by OS peculiarities or by inner peculiarities of
particular SDK version. Also there are some differences in nib reading
under several OS versions, which can't be uncovered unless you'll run
your app on that OS.
Hope this is more or less correct way to debug an app. Am I missing
anything?
Best regards,
Alexander
_______________________________________________
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