Linking Libraries in iOS?
<p>This is probably a totally noob question but I have missing links in my mind when thinking about linking libraries in iOS. I usually just add a new library that's been cross compiled and set the build and linker paths without really know what I'm doing. I'm hoping someone can help me fill in some gaps.</p>

<p>Let's take the OpenCV library for instance. I have this totally working btw because of a really well written tutorial( <a href="http://niw.at/articles/2009/03/14/using-opencv-on-iphone/en" rel="nofollow">http://niw.at/articles/2009/03/14/using-opencv-on-iphone/en</a> ), but I'm just wanting to know what is exactly going on. </p>

<p>What I'm thinking is happening is that when I build OpenCV for iOS is that your creating object code that gets placed in the .a files. This object code is just the implementation files( .m ) compiled. One reason you would want to do this is to make it hard to see the source code and so that you don't have to compile that source code every time. </p>

<p>The .h files won't be put in the library ( .a ). You include the .h in your source files and these header files communicate with the object code library ( .a ) in some way. </p>

<p>You also have to include the header files for your library in the Build Path and the Library itself in the Linker Path. </p>

<p>So, is the way I view linking libraries correct? If , not can someone correct me on this ?</p>
