Ken;
Thanks for the quick and helpful response!
You seem to have assumed that you can only compile against the 10.4
SDK by going back to Xcode 2.5 (and thus using an earlier compiler).
No I brought the application back to the 10.5 machine and have left it
compiling against the 10.4 SDK
On Oct 18, 2008, at 1:36 AM, Steve Cronin wrote:
...(bug fixes) which are only enabled for binaries linked against
the 10.5 SDK. This is both a good and bad thing. It means your
program works consistently on Tiger and Leopard, which makes
testing easier. But it might behave consistently
Ken;
Once again, thanks for the exemplary response!
(You are a great resource for the Cocoa community!)
So... while yes, the 10.5 SDK does have bug fixes, using it and
deploying to 10.4 potentially bifurcates the product into different
behaviors.
(It is really tough to determine where and
On Sat, Oct 18, 2008 at 9:55 AM, Steve Cronin [EMAIL PROTECTED] wrote:
Since my goal was to deploy to 10.4 all along, by using the 10.4 SDK, the
app will behave the same on both 10.4 and 10.5 (and 10.6) -- simpler from a
support perspective.
In some cases the behavior might be consistently
Folks;
I have developed an application with XC 3.1 on a 10.5 Intel machine
using the 10.5 SDK w/ a 10.4 deployment target.
(No GC for me!)
In testing I immediately ran into a few difficulties on a 10.4 PPC
machine.
In the course of tracking down these issues I ended up installing XC
2.5
On Oct 18, 2008, at 12:18 AM, Steve Cronin wrote:
I have developed an application with XC 3.1 on a 10.5 Intel machine
using the 10.5 SDK w/ a 10.4 deployment target.
(No GC for me!)
In testing I immediately ran into a few difficulties on a 10.4 PPC
machine.
In the course of tracking down
