Re: Private Frameworks

FROM : Philippe Casgrain
DATE : Sun Jan 13 16:19:28 2008

Kyle Sluder wrote:

> Assuming you're building your framework as part of the same project as
> your actual app, you can simply mark the role of the framework's
> header files as private, and #import them in your app's source using
> relative quoted paths like #import "FrameworkHeaderFile.h", rather
> than the typical #import <FrameworkName/HeaderFile.h> paradigm.
>
> You're still going to need to link the app to the framework and copy
> the framework into the app bundle's Frameworks directory, but this way
> you won't be copying the headers with it.


Note that if your framework contains Objective-C classes, there is 
nothing stopping interested parties from using class-dump (http://www.codethecode.com/projects/class-dump/
) to access the class information. In that case, headers help, but are 
not necessary...

Philippe