Re: Universal Binaries, x86 and compatibility...
Re: Universal Binaries, x86 and compatibility...
- Subject: Re: Universal Binaries, x86 and compatibility...
- From: Ali Ozer <email@hidden>
- Date: Wed, 8 Jun 2005 13:33:35 -0700
Many Cocoa apps don't have to do anything, however, can't say for
sure without seeing your sources or actually trying.
One step in the process is to make sure your sources build with gcc
4.0, which is a stricter compiler. So you might run into few build
warnings or errors you would have to fix.
In addition, some problematic code (such as divide by zero, sending
ObjC messages to nil and getting floats back, etc), act differently
on PowerPC and Intel; that could be another source of issues in your
bring-up, if you had such undetected problems in your code.
In any case, even if there are a few tweaks, it will likely not
require rearchitecting or rewriting hundreds of lines of code.
Ali
Begin forwarded message:
From: Keith Blount <email@hidden>
Date: June 8, 2005 13:14:14 PDT
To: email@hidden
Subject: Universal Binaries, x86 and compatibility...
Hello,
I am hoping someone can put my mind at rest about the
whole x86/Universal Binaries issue. I am developing an
app that will either be freeware or shareware, and
thus cannot afford the Transition Kit. I'm only just
now trying to get my head around Core Data as I had to
wait for the official release of Tiger to afford that,
and when I finally got it I found that a lot of code I
had spent a long time over was now redundant (not just
data stuff - I spent weeks and weeks on implementing
variable row heights in tables and lists in text
views). I'm not complaining, but it was frustrating.
And now it seems there is another major change coming
and again I won't be able to see how it affects my app
for some time...
So... am I safe in assuming - from reading various
comments and looking at the docs published with Xcode
2.1 - that the chances are that my app, which doesn't
do much more than use some custom views and use basic
AppKit/Foundation classes, will most likely just run
on an Intel machine once it is compiled as a Universal
Binary? It's not a big deal if the compatibility
issues are likely to be relatively minor and if it
will just mean ironing out some small bugs when the
new machines come out; what worries me is the idea of
having to rewrite hundreds of lines of code I'm
investing in right now a year or two down the line.
Sorry if this is a very basic question.
Cheers,
Keith
_______________________________________________
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