Making sure my code will run on Tiger 10.4 when I'm compiling on Leopard 10.5.
Making sure my code will run on Tiger 10.4 when I'm compiling on Leopard 10.5.
- Subject: Making sure my code will run on Tiger 10.4 when I'm compiling on Leopard 10.5.
- From: Ryan Poling <email@hidden>
- Date: Mon, 10 Dec 2007 16:24:31 -0800
I've been running into some issues developing a project on Leopard
(10.5.1) which I want to run on any version of Tiger (10.4.x) in
addition to Leopard. In Xcode, I've set my "Cross-Develop Using
Target SDK:" to "Mac OS X 10.5" and set my "Mac OS X Deployment
Target" to "Mac OS X 10.4." This should, theoretically, allow me to
use features present only in Leopard if I'm running on Leopard (like
the new animator), but also still run normally on Tiger.
Although this mostly seems to be working, I keep running into cases
where I've accidentally called some bit of Apple code which isn't
present until Leopard (NSURLRequestReloadIgnoringLocalCacheData was
the last one). I thought I was being pretty careful to check
everything, but I of course managed to miss a few. In order to figure
out what I missed, I ended up setting the target SDK back to Tiger and
compiling against that temporarily to see where the compiler
complained. This was a bit of a hassle since the compiler immediately
got stuck on NSUInteger and didn't give any more errors, so I
temporarily added the typedef to my code to force the compiler to move
on to the next error.
Anyhow, after the big rambling description, my question boils down to
the following: is the method I described above the best way to make
sure my code won't crash on Tiger, or am I missing some easier way?
Thanks,
-Ryan
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden