We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1374

Summary: iOS build fails for emulator
Product: SDL Reporter: Jack Jansen <Jack.Jansen>
Component: buildAssignee: Sam Lantinga <slouken>
Status: RESOLVED WONTFIX QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 Keywords: target-2.0.0
Version: 2.0.0   
Hardware: x86   
OS: iOS 4   

Description Jack Jansen 2012-01-16 02:01:05 UTC 
The iOS build fails when building for the emulator (it works fine for the device).

When I run
  xcodebuild -target libSDL -sdk iphonesimulator4.2 -configuration Debug
it tries to build for armv6/armv7, even though we're doing an emulator build. The problem seems to be that the armv6/armv7 architectures are hard-coded in the project, even for emulator builds.

The workaround is to run
  xcodebuild -target libSDL -sdk iphonesimulator4.2 -configuration Debug ARCHS='i386 x86_64'
but you may want to fix the projects.
Comment 1 Sam Lantinga 2012-01-16 16:29:41 UTC 
Interestingly, when I build from the IDE for the simulator, it knows to build i386:
CompileC /Users/slouken/Library/Developer/Xcode/DerivedData/SDL-gdscwliefsbcbahfvvdtczrpmwdq/Build/Intermediates/SDL.build/Debug-iphonesimulator/libSDL.build/Objects-normal/i386/SDL_render_sw.o ../../src/render/software/SDL_render_sw.c normal i386 c com.apple.compilers.llvm.clang.1_0.compiler

Is there a way to set per-output architectures?  I guess I could create a Debug-simulator target...

Is that what you want?
Comment 2 Ryan C. Gordon 2013-07-12 22:15:38 UTC 
(Sorry if you get a lot of copies of this email, we're touching dozens of bug reports right now.)

Tagging a bunch of bugs as target-2.0.0, Priority 2.

This means we're in the final stretch for an official SDL 2.0.0 release! These are the bugs we really want to fix before shipping if humanly possible.

That being said, we don't promise to fix them because of this tag, we just want to make sure we don't forget to deal with them before we bless a final 2.0.0 release, and generally be organized about what we're aiming to ship.

Hopefully you'll hear more about this bug soon. If you have more information (including "this got fixed at some point, nevermind"), we would love to have you come add more information to the bug report when you have a moment.

Thanks!
--ryan.
Comment 3 Sam Lantinga 2013-07-13 00:51:41 UTC 
Works fine from the IDE, Jack has a workaround, and no response in over a year.
Closing!