Question

I have code that I build into a framework. It is sometimes useful, when debugging other project code relying on the framework, to instead build the source into the other project directly. The only issue is the way headers are referenced:

// Framework
#import <my_framework/my_widget.h>

// Source
#import "my_widget.h"

I could make a bunch of edits and go on my way, but I feel like there must be a clever solution to this, perhaps related to setting something for the Framework search path.

I’m curious about doing this in Xcode, though the raw command would also be useful.

Update

Despite some sensible advice, I’m having trouble getting this to work, so more explicit help would be great (and hopefully helpful to others).

// My framework source directory
/work/my_framework_project/source/widgets/my_widget.h
/work/my_framework_project/source/widgets/my_widget.m

// The framework that creates
/work/my_framework.framework/my_framework
/work/my_framework.framework/Headers/my_widget.h

// The project I'm debugging
/work/some_project/source/my_source.m

If I drop the framework into some_project, I refer to my header like this:

#import <my_framework/my_widget.h>

If I drop the reference to framework and add the source to the project, I need to do this, but don’t want to:

#import "my_widget.h"

Note that I do not import "my_framework/my_widget.h" — if that matters.

If I follow the first suggested answer, then I add this as a flag to the source files when I’m compiling them (currently by adding it in the “Compile Sources” area.

-I/work/my_framework.framework/Headers

This is not solving the issue of wanting to refer to the imports using the framework notation.

Answer 1

though the raw command would also be useful

Here it is:

<COMPILER> -Imy_framework_dir <other options...>

So you use the -I (uppercase ‘i’) flag for this (GCC or Clang style).

Xcode supports this feature using the ‘user search header paths’ section on the ‘Build phases -> Compilation’ tab of your project.