A crash tends to be one of the easiest type of bugs to track down. Make sure
you've got CrashReporter turned on and that you're reading the PPC section
below the Rosetta info. And, if you haven't ran it on OS X lately, you may
want to make sure you're not doing any typecasts when you should be using
functions; some of those methods were fine in the early days of OS X but as
time progressed, those opaque and non-compatible data structures actually
became far different than their OS 9 ancestors. Also, you may want to try
bringing it into Xcode against the 10.3.9 SDK rather than the 10.4 SDK;
some of
the headers in the 10.4 SDK can get tricky if you've got an old CodeWarrior
header dependency (and, that was even true with CodeWarrior on 10.4).
Of course, my theory on the "deprecation" of Carbon (can't really say
that this
is the case, though) is that Apple's now at a place to promote the
"yellow box"
that was promised years ago, which is being "shown" via Safari on
Windows. And,
if you recall how many gyrations we were going to have to do just to
get working
on the first version of Mac OS 8, then I'm glad we've had a lot more
transition
time before this supposed "writing on the wall."
P.S. It was that version, 8, wasn't it, that was going to require major
rewriting just to move forward?
Quoting Tony Scaminaci <email@hidden>:
I have an old application that's 100% carbon and was developed under
OS 9 just before the advent of OS X. I recently tried bringing it
into XCode from Codewarrior and that was a total disaster. While I
got it to build using heroic-style antics, it crashed in numerous
places so I finally gave up. So here I sit, trying to figure out what
to do with this app that I still want to use. Dump it forever, go
through the pain of bringing it into the modern world of XCode,
change the entire user interface to Cocoa? What to do, what to do...
So far, my solution is to do nothing. The carbon version runs fine
under OS X, at least on the PPC platform. I tried running it under
Rosetta on my MacBook Pro and most of it ran correctly...and then the
ole' crash. So I guess it won't be running on my brand-spanking new
MacBook any time soon. I have a full time job and this looks like way
too much work to convert. If I ever need to update it, I can always
boot back into OS 9 and run Codewarrior. But how it'll ever get to
the Intel platform is beyond me...
Tony
On Jun 13, 2007, at 2:45 AM, Jerry wrote:
I'm one of the niche people who need 64-bit - we deal with 200+Gb
images all day. We're using a cross-platform toolkit to run on Mac,
Windows and Linux, The Mac stuff is all Carbon-based and this is
going to be a real blow and will probably spell the end for our
product on the Mac. The other platforms already have 64 bit
versions - we've just been waiting for 64 bit support on the Mac. I
suspect the Mac version of our app is probably just going to fade
away. There's no chance we're going to switch toolkits.
Jerry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
