Skip to main content

iPhone Compiler Fails: No architectures to compile for



Hey guys, I'm trying to implement this in my iPhone app: http://code.google.com/p/core-plot/downloads/detail?name=alpharelease_0.1.zip&can=2&q=&sort=-uploaded . I figured I'd first try to run the sample they provide. I'm attempting to open and compile the project located in /Source/examples/CPTestApp-iPhone/ . It says my base SDK was missing right off of the bat, so I edited the Project settings and the Active Target to use the iOS4 SDK, which I've done before for samples and had work. I'm not sure what to do. I'm running one of the newest Unibody Macbooks, with 10.6.4.





Here is my full error:







// - start - //



Check dependencies



[BEROR]No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=i386, VALID_ARCHS=armv6 armv7).



// - end - //







Thoughts?





Thanks!





  • Josh




Comments

  1. Try this:

    Project Build Settings:


    Architectures: Standard (armv6 armv7)
    Base SDK: Latest iOS Build Active
    Architectures Only: Checked Valid
    Architectures: armv6 armv7


    Delete any sub settings in the Architecture build setting.

    Target Build Settings:


    Same at project settings.


    Frameworks
    Add the SystemConfiguration.framework to your project. - Not sure why this had any impact.

    Clean all targets.
    Build for the simulator.

    The long explanation for this can be found on our blog: http://longweekendmobile.com/2010/06/15/fixing-the-missing-required-architecture-arm-in-file-when-developing-for-ipad/

    ReplyDelete
  2. I also went to the Build settings for the target(s) that failed and added "i386" to the valid architectures

    ReplyDelete
  3. Adding i386 to the Valid Architectures list worked for me!

    ReplyDelete
  4. You have selected as active architecture "active arch=i386 (your Mac)" but the project compiles for " VALID_ARCHS=armv6 armv7 (iPhone Device)", try setting the right arch in the project settings, so it is built for iPhone as it should be.

    ReplyDelete
  5. For me it was that I had to add i386 to the VALID_ARCHS list. Odd, but it fixed my problem for simulator builds.

    See this post.

    ReplyDelete
  6. This project appears to pre-date iOS 4, so you need to open up the .xcodeproj file for the Core Plot library itself, too. It probably also has a broken reference to an old iOS Base SDK and may need the architectures updated.

    ReplyDelete
  7. This happens all the time with old projects migrated to SDK 3.2/4.0. You have to open the target settings and change everything to SDK 4.0 or 3.2. You can still have the target OS be 3.0 if you want that. If it still says "missing SDK" you neglected to change one of those settings to 4.0 or 3.2.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex