Codewarrior 9.4 on Macintosh

[larryb]

I have used Codewarrior for many years for a freeware application for the Macintosh. It is now time to convert to XCode. I am first converting the project to a MachO application. I am using CW9.4 and XCode 2.5. After creating a MachO target, I find that I cannot debug my original target (carbon) code. When I start the debug version, there is a long pause and the application starts up without the normal start screen at the beginning of the code. Codewarrior does not stop at any breakpoints. When I quit the application, there is a long pause. When I try to run the application again (in debug) mode, I get the message that "The process is already starting".

Does anyone know what is going on? I tried upgrading to Codewarrior 9.6. I downgraded to XCode 2.2. I removed Codewarrior and reinstalled. It seems like once I created a MachO target, some switch got changed which will not allow me to debug my non-MachO (carbon) target.

Thanks for any advice.

[J2MEJediMaster]

Freescale no longer supports the Mac and Windows desktop version of CodeWarrior. However, I'll try a shot at an answer here.

The mach-o code uses a completely different calling and access conventions from Carbon, which uses code objects called code fragments. The two are incompatible, so that would explain why once you've set the build target up as mach-o, you can't go back to debug Carbon code. You probably need to set up two projects, one with a Carbon target and one with a mach-o target.

I don't know enough about the last Mac versions of CodeWarrior to explain the odd behavior. Sorry.

---Tom

[larryb]

Thanks for the advice. I did decide that I should probably use two different projects for this with one for mach-o and one for carbon. But I still have the same problem. It seems like a switch was change somewhere ... in a .plist file, etc that does not allow the normal debug with carbon to work. I did find one other question about this same problem yesterday on another web forum site dated about 18 months ago but there were no answers for it.