StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I did the following to make it work for me:</p> <ol> <li>for the three20 static library, I used <a href="http://cocoapods.org/?q=three20" rel="noreferrer">cocoapods</a> to include the files within the main project.. it just got rid of all the trouble three20 was giving me (and they are lots..) btw i tried replacing three20 with <a href="http://nimbuskit.info/" rel="noreferrer">Nimbus</a>.. but Nimbus was lacking on some of the features that my project was using three20 for.. so Nimbus wasn't helpful.</li> <li>set skip install to yes under build settings for all other sub projects/static libraries and switched the copy headers from public to project under build phases</li> <li><strong>most importantly:</strong> under the sub libraries.. under build phases i ensured that <strong>copy files</strong> destination was changed from <code>Absolute path</code> to <code>products directory</code>. </li> </ol> <p>and that was it! </p> <p><strong>hint:</strong> to get an idea of the offending files that's causing your archive to create an archive file rather than an ipa do this:</p> <ol> <li>Select the archive and click the Distribute button. </li> <li>Select the 'Save Built Products' option. </li> <li>Hit Next and Save. </li> <li>Browse the created directory in Finder. </li> <li>The 'libraries' subdirectory will identify the libraries that you need to set the Skip Install to Yes. </li> <li>in some cases <code>usr/local/include</code> will identify the culprit header files you need to move from Public to Project or the files that you have to change from absolute path to products directory. but that directory (ie usr/local/include) varies depending on your sublibrary directory structure</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