Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>Please see <a href="https://stackoverflow.com/q/5319155/89035">this question</a> for additional detail.</p> </blockquote> <p>The accepted answer doesn't fully solve the problem for all projects. There are several issues that all relate to each other and I will cover them all.</p> <h1>Xcode 4 Project Fails to compile a static library</h1> <blockquote> <p>Related question: <a href="https://stackoverflow.com/q/5543854/89035">Xcode 4 can't locate public header files from static library dependancy</a><br> Related question: <a href="https://stackoverflow.com/questions/5584317/lexical-or-preprocessor-issue-file-not-found-in-xcode-4">“lexical or preprocessor issue file not found ” in Xcode 4</a></p> </blockquote> <p><strong>Errors might include;</strong> missing header files, "lexical or preprocessor issue" </p> <p>Solutions: </p> <ol> <li>Check the "user header paths" are correct</li> <li>Set "Always search user paths" to YES</li> <li>Create a group call "Indexing headers" in your project and drag the headers to this group, <em>DO NOT</em> add to any targets when prompted.</li> </ol> <h1>Xcode 4 project with static library dependancy fails to create a valid archive</h1> <blockquote> <p>Related question: <a href="https://stackoverflow.com/q/5271496/89035">https://stackoverflow.com/questions/5271496/xcode4-ios-4-3-no-packager-exists-for-the-type-of-archive</a></p> </blockquote> <p><strong>Errors might include;</strong> </p> <p><img src="https://i.stack.imgur.com/jvsXv.png" alt="Xcode 4 project with static library dependancy fails to create a valid archive"></p> <p>Missing identifier and version. "No Packager exists for the type of archive"</p> <p>Solutions:</p> <ol> <li>For all dependancies set <strong>"Skip Install"</strong> build setting to <strong>"Yes"</strong></li> <li>Moving any "Public" headers in Build Phases to "Project"</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload