On Apr 9, 2008, at 11:08 PM, Ben Lachman wrote:
On Apr 9, 2008, at 3:27 PM, David Duncan wrote:
On Apr 9, 2008, at 7:43 AM, Lorenzo Bevilacqua wrote:
I'm trying to build a Cocoa application so that it can run on Mac
OS X from version 10.3.9 to 10.5.
I have 10.5 installed so the application
On Apr 10, 2008, at 6:19 PM, Chris Suter wrote:
One caveat, though, is that you should probably have a runtime
check for the minimum OS version you expect so that you don't end
up with a crash if someone tries to use your nifty Leopard
features on Tiger. Adding something to main() would
On Apr 9, 2008, at 11:08 PM, Ben Lachman wrote:
On Apr 9, 2008, at 3:27 PM, David Duncan wrote:
Typically you would only use 1 target. Use the SDK to the OS whose
API your are targeting (such as the 10.5 SDK). Then set the
deployment target to the minimum version you wish to run on
On Fri, Apr 11, 2008 at 12:26 AM, Jerry Krinock [EMAIL PROTECTED] wrote:
That's fine if the classes exist in all the OS versions, but more commonly
you'll want to use complete classes that are not available in earlier SDK,
of which there are many, especially in Leopard. Code instantiating
Hi,
I'm trying to build a Cocoa application so that it can run on Mac OS X
from version 10.3.9 to 10.5.
I have 10.5 installed so the application runs fine on my system and on
other Leopard systems.
I haven't build a project for multiple platforms yet, so I tried to
duplicate the main Xcode
Using Obj-C 2.0 can give a little speed boost over previous versions
of Mac OS X. For building for other system versions sometimes you
need to link to the SDK of that version if you find some symbols are
missing (depreciated or removed). If you want to use certain features
on one
- Does the Objective-C 2.0 fast enumeration make sense to be used? I
mean, if I don't use it, will my application perform worse on Leopard?
Unless you are doing a huge number of enumerations, the difference is
speed will not be worth the extra coding hassle. Better check the
difference
