Whenever you support an earlier OS, you should always have that earliest and all intermediate SDKs available, and you should make it a standard practice to build your products against those SDKs at least before releasing to customers just as you do an analyzer build. This will help you identify many of the cases where you need to safeguard against the use of unavailable APIs, methods, and classes. Oh, and you really should be turning on and listening to practically every warning possible. Then, after you do all that, testing definitely should be done. -- Gary L. Wade (Sent from my iPad) http://www.garywade.com/
On Jun 28, 2012, at 8:13 AM, Charles Srstka <cocoa...@charlessoft.com> wrote: > On Jun 27, 2012, at 2:53 PM, koko wrote: > >> Ok, so what is the real truth regarding using a base SDK of 10.6 and a >> deployment target of 10.5? >> >> The blogosphere says this cannot be done and Apple says it is OK. >> >> We have issues running a 10.6 SDK build on a 10.5.8 system. >> >> We have a certain percentage of customers who are on 10.5.8. >> >> Who should I believe? Apple or the blogosphere? > > It can definitely be done in theory. > > In practice you have to test the heck out of it, because without the 10.5 > SDK, there’s nothing keeping you from accidentally using 10.6+ APIs, whose > effects will only show up by throwing runtime exceptions on 10.5. > > Charles _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
