About Universal Binaries...
About Universal Binaries...
- Subject: About Universal Binaries...
- From: "Juan P. Pertierra" <email@hidden>
- Date: Tue, 31 Jan 2006 20:06:43 -0500
I have a cocoa application which I will be adapting to Intel soon.
I have a simple question: From an initial look to the online Apple
transition documentation it seems all the differences that have to be
addressed span from the difference in byte order i.e. big endian vs
little endian.
Is this the case? Or are there other hardware differences that I
will need to be aware of in adapting my current Objective-C code?
Cheers,
Juan
On Jan 31, 2006, at 8:01 PM, Shawn Erickson wrote:
On 1/31/06, Aram Kudurshian <email@hidden> wrote:
I posted a while back ago about converting a method I had to work
with universal binaries and had thought that the following code would
have solved the issue. Turns out I was wrong and now, re-reading
information online, I'm wondering if the only reason this compiled is
because Xcode simply ignored what was contained in the #else as I was
compiling on a PowerPC machine.
Are you building a universal binary? If you are it doesn't matter what
system you are building on since by definition your code is getting
compiled twice, once for PowerPC and once for Intel.
When is compiles for PowerPC the pre-compiler should leave you with
the first block and when it compiles for Intel you should get the
second block.
Anyway what are you seeing fail in the debugger?
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
stream.com
This email sent to email@hidden
_______________________________________________
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