Anders F Björklund wrote:
> Probably could have made a version with the MacOSX10.3.0.sdk, but it's better to force upgrading to 10.2.8 and 10.3.9... :-)
> 
> Besides, you probably *want* Mac OS X 10.3.9 anyway for the security fixes, and for the compatibility with GCC/G++ 4.0 ?

Yeah, upgrading isn't an issue, I just hadn't got around to it.

By the way, will end-users have to be patched to 10.3.9 in order to run the compiled programs? (And what about 10.2.x and 10.4.x?)

Chris Pelling wrote:

> By the way, will end-users have to be patched to 10.3.9 in order to run
> the compiled programs? (And what about 10.2.x and 10.4.x?)

It's all about the libraries. End users shouldn't have to upgrade unless they encounter some issues like you had, but better put a disclaimer in.

In general, the ready-made binaries will support the latest OS version.
But I don't have any code that requires the new OS, just a side-effect.

I don't think there will be any more explicit Mac OS X 10.2 versions of GDC, so you'll have to use Panther to develop for Jaguar in that case...

--anders