ansaurus

Question

Suddenly I am not able to build for the iphone simulator...

Answer 1

A:

It is very frustrating. Are you able to compile other projects to the simulator?

In one case, I ended up starting a whole new project and bringing all my assets and files in. That sounds really bad, but it was painless compared to trying to isolate whatever it was I had done to break it.

Nosredna 2009-09-21 01:08:03

I follow your approach sometimes. However, not figuring out where the problem is, is likely going to cause you to fall into the same problem again. Better spend time figuring it out first time, unless you are under a tight deadline

hhafez 2009-09-21 02:30:48

True. But sometimes if you can get it working as a new project, you can compare that to the non-working project to see what the difference is.

Nosredna 2009-09-21 03:22:12

Yes, I am able to build for the iPhone 3.1 device no problem. This is just happening with the Simulator. The simulator is an i386 platform while the device is an arm. I do not know the magik of Xcode well enough...

2009-09-21 03:48:39

I'm asking if you can build other projects (like examples) for the simulator (not the device).

Nosredna 2009-09-21 04:48:21

That's not the question. If you create a brand new project, can that compile for the simulator? If not, then try installing the latest XCode on the iPhone development portal. If you can compile that for the simulator, make a new project with the same name and just copy all of the files you have now into that new project.

Kendall Helmstetter Gelner 2009-09-21 04:49:57

For whatever reason, the project got corrupted - I was able to create a new project and carefully copy all the files over. What a royal pain in the arse!!!!

2009-09-21 16:15:57

Well I'm glad you finally got it working. I had similar things happen 2 or 3 times.

Nosredna 2009-09-21 16:29:23

Answer 2

A:

Have you downloaded the new Xcode from the Apple iPhone Developer Center/page/thing? The Xcode shipped with Snow Leopard does not come with the iPhone libraries; those are only available after downloading the awesomely sized 2+gig developer package.

Malaxeur 2009-09-21 03:16:03

Yeah, I have the most recent SDK and installed the Simulator package. Both directories are present in the /Developer/Platforms directory.

2009-09-21 03:50:53

Answer 3

+1 A:

It's trying to link against the iPhoneOS.platform when it should be linking to the iPhoneSimulator.platform

When you expand the Link build result, this is what your should see:

setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/g++-4.2 -arch i386 -isysroot /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk

I can only suggest playing with the Base SDK and iPhone Deployment Target properties of your target's build settings and your project's build settings.

Other than that, I'd guess it's a problem with your XCode install rather than your project.

Darren 2009-09-21 04:13:59

Answer 4

+1 A:

Thanks to Nosredna. XCode is really the crappiest IDE ever. I have to say that it is even worse than Eclipse. You would think that after all these years there would be sometime on par with Jetbrains IntelliJ for Java.

For whatever reason, as in, while I was actually working on the project and not doing any XCode voodoo magik, it apparently got corrupted. In the end I wasted a few hours twittling with the build and linker parameters only to end in sadness and despair.

Coming from the world of Java, with tools like IntelliJ, it is a little bit of a struggle when dealing with this Magik, as in XCode and IB. On several occasions now I have had to throw away my NIB because something went wrong. When you crack open the XML in the hope of fixing it, well, lets just say it is faster to reconstruct a new view controller with nib. LAME.

To recap - if your project suddenly goes to lunch, it is likely XCode and just be warned of the time sink if you are thinking that you are going to fix it.

2009-09-21 16:27:01

Check out my answer (and link) for a simple explanation on how to fix this issue. It's true that Xcode does some strange things, but it's not really too bad in the long run. It's usually just a build setting (and in this case, one that follows quite logically from the error).

John Cromartie 2009-09-23 19:50:48

Answer 5

A:

I just solved this issue for myself today. See my answer here: http://stackoverflow.com/questions/1456185/build-error-missing-required-architecture-i386-in-file/1467238#1467238

John Cromartie 2009-09-23 16:48:51

ansaurus

tags:

views:

answers:

Suddenly I am not able to build for the iphone simulator...

related questions