StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p><em>NB: The steps below will solve 90% of your Xcode archive issues however, from the comments it is suggested you try <a href="https://stackoverflow.com/questions/5584317/lexical-or-preprocessor-issue-file-not-found-in-xcode-4/5771913#5771913">quitting Xcode</a> first. This may save you hours of setting tweaking.</em></p> </blockquote> <ol> <li>Check the "user header paths" are correct (Add "" to paths for spaces, both in your project and dependencies)</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. This includes any headers inside your <em>.xcdatamodeld</em>, you'll need to right-click and view package contents to find them. </li> <li>For all dependencies set <strong>"Skip Install"</strong> build setting to <strong>"Yes"</strong></li> <li>Moving any "Public" headers in Build Phases to "Project"</li> <li>Set the Build Setting <strong>"Installation Directory"</strong> on your Target to <code>$(LOCAL_APPS_DIR)</code></li> <li>Change the target build setting "scan all source files for includes" to YES. (<a href="https://stackoverflow.com/questions/5584317/compile-build-or-archive-problems-with-xcode-4-and-dependancies/7211009#7211009">link</a>)</li> <li>With newer versions of Xcode (> 4.2) you might want to <a href="https://stackoverflow.com/questions/5534235/how-do-you-get-implicit-dependencies-to-work-with-workspaces-in-xcode-4/8116994#8116994">read this question</a> related to workspaces.</li> <li>Manually <a href="https://stackoverflow.com/a/6356862/89035">delete the project.xcworkspace files</a> form all referenced projects</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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