Note that there are some explanatory texts on larger screens.

plurals
  1. POiPhone - Static libraries, purpose of "Copy Headers"?
    text
    copied!<p>I am creating a library and even though it is working perfectly fine by packaging all my code and putting all the header files in a folder and then zipping the folder and the static library, I just can't figure out the purpose of the "Copy Headers" section under Build Phases.</p> <p>I have read all this links:</p> <p><a href="http://blog.carbonfive.com/2011/04/04/using-open-source-static-libraries-in-xcode-4/" rel="nofollow noreferrer">Using open source static libraries</a></p> <p><a href="http://www.icodeblog.com/2011/04/07/creating-static-libraries-for-ios/" rel="nofollow noreferrer">Creating static libraries for iOS</a></p> <p><a href="http://blog.boreal-kiss.net/2011/03/15/how-to-create-universal-static-libraries-on-xcode-4/" rel="nofollow noreferrer">How to create universal static libraries</a></p> <p><a href="https://stackoverflow.com/questions/7439192/xcode-copy-headers-public-vs-private-vs-project">Stackoverflow: copy headers: public vs private vs project</a></p> <p>But I still do not see the point of setting the copy headers, I realize you can set the private and public path under build settings > packaging, and that the header files will go to that folder after build. But what is the point in this?, is this any different than not setting a single copy header file, and simply grabbing the .a file grab all my header files and put them in a folder?. Also what is the purpose of setting copy project headers?, since they are not included in the target at all?.</p>
 

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