Re: Universal Binaries, x86 and compatibility...
Re: Universal Binaries, x86 and compatibility...
- Subject: Re: Universal Binaries, x86 and compatibility...
- From: Óscar Morales Vivó <email@hidden>
- Date: Wed, 8 Jun 2005 13:44:02 -0700
A Cocoa app that doesn't go low-level shouldn't have any issue going
to intel.
I suggest you first do as Ali Ozer says and make sure you're
compiling on GCC4.0 and solving any new errors/warnings you might
find in an elegant way.
After that I'd like to think you'll probably can get help seeing if
the thing runs on a PentiumMac from someone with access to one, as
the expected amount of work in your case would be extremely small. I
know for one that I wouldn't have much of a problem checking it (I'll
have access to one of those machines once they start shipping).
Even then, it's at least 6 months until Intel macs start appearing in
shops, so you have plenty of time to complete developing your app.
Repeating myself, you should find zero or very minor issues with
porting to Intel for a clean Cocoa app so you probably can afford to
wait until those are out to make it work.
Hope that helps:
Óscar Morales Vivó
On Jun 8, 2005, at 13:14 , Keith Blount wrote:
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 you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
_______________________________________________
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
_______________________________________________
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