views:

13

answers:

1

Am I supposed to adjust FRAMEWORK_SEARCH_PATHS or HEADER_SEARCH_PATHS when I add custom frameworks to the project?

I have MainProject.xcodeproject that links SomeFramework.framework that's simply dragged from "Products" in SomeFramework.xcodeproject to "Link with Binary Libraries" build phase in main project.

Framework contains all required headers in its Headers directory. However, in my project I can't simply use:

#import <SomeFramework.h> // I'm pretty sure this file exists

to include this header. Build fails "No such file or directory". Compiler flags include -F…/SomeFramework/build/Release and that directory contains framework with Headers directory symlink in it.

(BTW: this is for Mac OS X. I don't care about iPhone.)

+1  A: 

Just adding the path to the directory containing the framework to FRAMEWORK_SEARCH_PATHS will work. Unless it's a typo, your problem seems to be

#import <SomeFramework.h>

which should be

#import <SomeFramework/SomeFramework.h>
w.m
It wasn't a typo! I'm half-there. Now the second problem is that `SomeFramework/SomeFramework.h` contains `#import <SomeFrameworksOtherHeader.h>`. Is that the same error in the framework too?
porneL
Yes, in that case it should be #import "SomeFrameworksOtherHeader.h"
w.m