Re: Determining how the app is run (intel/ppc/rosetta/os version)?
Re: Determining how the app is run (intel/ppc/rosetta/os version)?
- Subject: Re: Determining how the app is run (intel/ppc/rosetta/os version)?
- From: glenn andreas <email@hidden>
- Date: Fri, 26 May 2006 16:45:41 -0500
On May 26, 2006, at 2:48 PM, Gerben Wierda wrote:
My app contains:
x86 binary compiled with gcc 4 against 10.4 SDK
ppc binary compiled with gcc 3 against the 10.3 SDK to make sure
it is compatible with 10.3 on ppc
The ppc binary is a known trigger of the partial OS freeze bug of
10.4.6
The x86 binary does not work properly on 10.4.4 - 10.4.6 (on x86)
[Note: if I compile the ppc with gcc 4 against the 10.4 SDK it also
does not work properly on ppc hardware. This seems to be a myApp/
Tiger issue which does not occur when I compile with gcc3 against
the 10.3 SDK. I do not know yet what triggers it)
So, I want to make sure that the app
- exits with a warning when run in rosetta on 10.4.6
- exits with a warning when run natively on 10.4.4-10.4.6
(assuming that 10.4.7 will be OK again and I have good reason to
hope so)
So basically it appears that you're saying that the Intel version
doesn't work on any shipping system (and may, or may not, on a future
system). So why is it even a universal app? Definitely seems easier
to just ship a PPC only version until an OS version has been publicly
released that you've qualified as working (rather than shipping code
that requires an untested unreleased OS).
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
Widgetarium | the quickest path to widgets
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden