-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xcode 4 GM issue #59
Comments
Same here. |
You crazy kids need to stop using xcode 4 ;)... I'll look into the problem. Based on that error, its a silly error. |
After going through all targets, pressing delete on all Build only active targets, setting targets to Mac OS and then back to iOS, many many places, it now works. But still not a real solution. Also xcode4 finds insane amount of warnings, semantic some warnings |
traustitj can you share the final project that works on you machine? I wasn't able to make mine work yet. |
One workaround I used is to add "i386" to "valid architectures" setting (besides armv6 and armv7). |
It worked for me as well when I did it everywhere. Thanks! |
I had the same errors. The fix for the error (simulator only) is the add i386 to valid architectures setting. The fix for the compiler warnings is to change every instance of: if (self = [super init]) { to if ((self = [super init]) { In all the init methods. The problem was that xcode 4 is intelligent and thinks (correctly) that the majority of assign not compares in if statements are meant to be compares, so warns you. I'll code up a fix for these two problems and push it. |
I came up against the same issue. Fixed by specifying 'iOS device' as my target platform from the Scheme selector, top-left (and making sure all projects and sub-projects had 'build active architecture only' set to NO - not sure if that made a huge difference). It's indicative of a problem in a project settings file... Adding i386 to the valid architectures setting is probably not advisable. ;) (I am, however, getting some weird linker errors on trying to build libTapkuLibrary (TKCalendarMonthView) - trying to work out what that's all about now) |
@oioistudios what is the linker error exactly? There is known bug in linker that ships with XCode 4, and there are two workarounds:
I agree that setting i386 is not advisable - but I was desperate :) |
Actually, I stand corrected. I do believe i386 is a valid architecture (the Simulator!) Yeah, just discovered that bug re: LLVN linker and optimisation. I set the optimisation level on TapkuLibrary to -O1 (I don't actually need debug symbols from tapku in my current project, anyway) and that worked like a charm. Thanks! :D |
For me the error went away just by selecting: |
i've did this: http://cl.ly/59gg i think everyone should search for the framework settings not only the project. Problem solved. |
I didn't need to include the i386 |
I fixed the error and removed the build warnings too with the latest commit. If you see this issue with other projects, you can find the fix here https://devforums.apple.com/message/374009. |
When trying to run the universal demo I get the error
Check dependencies
[BEROR]No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=i386, VALID_ARCHS=armv6 armv7).
All the settings I see have picked Latest iOS 4.2.
The text was updated successfully, but these errors were encountered: