Hi John, Also worth noting: you can build on Leopard with Xcode 3.x, using the 10.4 SDK, and your app might run fine on a Leopard box. BUT, you still need to test on a native Tiger platform because the systems dylibs are different (and yes, the 10.4 API behaves differently between Tiger and Leopard). Even though you link against the 10.4 SDK, you still run against the system dylibs shipped on the target computer. Which is why you need to run on a native Tiger system for complete testing. Around here we figure that we need to keep a Tiger computer around for as long as we support Tiger.
Another note: be sure that you target 10.4 in your build environment. In particular, be sure that -mmacos-version-min=10.4 and -isysroot /Developer/SDKs/MacOSX10.4u.sdk are set as gcc build flags in case you are using makefiles. This will ensure that the generic (G3-friendly) ppc arch is built, and not the later ppc7400 arch (not supported on Tiger and some early Leopards). - Dave.S On Sun, Jan 25, 2009 at 1:01 PM, John Joyce < dangerwillrobinsondan...@gmail.com> wrote: > > On Jan 24, 2009, at 8:31 PM, cocoa-dev-requ...@lists.apple.com wrote: > > Not sure what you mean by "capable of running tiger". If you have a >>> machine >>> capable of running Leopard, it should be able to run tiger. >>> >> >> Not true. In general, any Mac requires the latest OS available at the >> time it was released. So machines released after the release of >> Leopard usually require Leopard. >> > > > Not in general. No Mac is supported to run any version of the Mac OS > earlier than the version it officially shipped with. > If your Mac officially shipped with 10.5.4 it is unsupported to run 10.5.3 > or earlier. Period. > If you do not know, and you may not, call AppleCare, provide the serial > number of the Mac, they can tell you precisely which version it originally > shipped with and that will be the earliest version you can reliably run on > that computer. > Although in some cases you may successfully boot and run some earlier > version, it is unsupported, meaning it would not be a good test > environment. > > Any Mac that runs Tiger well, will be more than adequate for most Tiger > development. (exceptions would be targeting higher or lower end hardware) > _______________________________________________ > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/dspringer%40google.com > > This email sent to dsprin...@google.com > -- http://go/OnlyCheckEmailTwiceADay - join the movement _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
