XCode project complains about missing files if a linked framework contains private headers

Posted by darklight on Stack Overflow See other posts from Stack Overflow or by darklight
Published on 2010-04-27T14:35:50Z Indexed on 2010/04/28 4:33 UTC
Read the original article Hit count: 332

Filed under:
|
|
|
|

My Problem is this:

  • My framework contains public and private headers - the public headers import private headers in the framework
  • My app that links against this framework imports public headers

Now when I compile it, XCode complains about missing files (the private headers that are indirectly imported via the frameworks public headers). I read somewhere on stackoverflow that I should do this:

"In the public header file use @class to include other interfaces and use #import in the implementation file (.m)."

I find this solution pretty unsatisfying - you have to use it for circular dependencies, too. Is there any better way to keep my headers private?

© Stack Overflow or respective owner

Related posts about cocoa

Related posts about gcc