Have you set the scope of the necessary header files to public?

file:///Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.DeveloperTools.docset/Contents/Resources/Documents/documentation/DeveloperTools/Conceptual/XcodeBuildSystem/100-Targets/bs_targets.html

On 09/06/2010, at 11:20 AM, Chris Tracewell wrote:

> I just made my first private framework a few weeks ago. I took some common 
> categories and custom classes I use across projects and put them in my new 
> FW. All has been fine until today when I added a new class file to it. I 
> clean and build the FW and then build my project that is utilizing the FW and 
> I get an error saying there is "No such file or directory" - referring to my 
> new class file in the FW. FWIW, I use #import <MyFramework/MyFramework.h> in 
> my project as it imports all the FW headers - standard protocol.
> 
> After I build the FW I look in "MyFramework -> build -> Release -> 
> MyFramework.framework -> Headers" and can see the header is indeed missing. I 
> know this is the correct directory because I can see MyFramework.framework 
> being deleted when I clean the FW target.
> 
> Why would it not be exporting the file? Yes, I added it to the target when I 
> created the file.
> 
> Thanks for the help
> 
> 
> -Chris
> 
> 
> _______________________________________________
> 
> Cocoa-dev mailing list ([email protected])
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/kiel.gillard%40gmail.com
> 
> This email sent to [email protected]

_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to