"Bad CPU Type In Executable"

Question

After upgrading from an eMac to an Intel Mac Mini, I noticed that I needed to reinstall Xcode. Once I reinstalled Xcode (v2.4), I made some changes to one of my applications. After testing it fully on my new Mac, I copied the .app file to my old eMac and attempted to re-run. In doing so, I received the following error message:
"You cannot open the application 'NAME OF APPLICATION' because it may be damaged or incomplete."
So, in Terminal, I navigated through the Package Contents to the actual executable and tried to run it. I, then, received the following error:
"Bad CPU type in executable."
How do I correct this error, so it will run on both of my Macs??
THANKS IN ADVANCE!!
WBELL
eMac Specs:
1GHz, 768MB DDR, OSX 10.4.x
Mini Specs:
1.5GHz Core Solo, 1024MB DDR2, OSX 10.4.x
Mac Mini Mac OS X (10.4.7) 1.5GHz Core Solo

Answer 1

Here are a couple of things to check...
First, from your screen shot it appears that the main.m file is from an older AS Studio application (ie is this a project that was originally created some time ago... perhaps under Project Builder?). The main.m file that gets included with relatively new AS Stdio apps looks like this:
<pre>
extern void ASKInitialize();
extern int NSApplicationMain(int argc, const char *argv[]);
int main(int argc, const char *argv[])
ASKInitialize();
return NSApplicationMain(argc, argv);
</pre>
So you may want to copy/paste the main.m code from a newly created AS Studio app into your (older?) existing project. I'm not sure the above problem would cause the failure to build a Universal app, but changing code in main.m may get rid of the warnings you're seeing.
But also, the screenshot made me wonder if your target(s) needs to be converted to the newer "native" target format (this is different from the "conversion" that Xcode does to an older project file). With your project open click on Xcode's "Project" menu... is the option "Upgrade 'YourTargetName' to Native Target" or "Upgrade all Targets in Project to Native" available? If so, I think you must convert to native targets in order to build universal binaries.
Hope this helps,
Steve