A framework header cannot find its own header files in Xcode?

Question

In Xcode, suppose that there is a framework named Foo. Inside the Foo.framework/Headers folder there are files File1.h and File2.h. The header file File1.h includes File2.h via the following directive:

#include <File2.h>

The Foo framework is a re-package of a C++ library not specifically targeted for the Mac.

Now suppose I have a project that links to the Foo framework. It has a file MyFile.mm that includes File1.h via the following directive:

#import <Foo/File1.h>

Now when I tried to compile MyFile.mm, it always fails because it can't find File2.h. How can I get this to compile and run without modifying the header files of the Foo framework?

For the curious, the actual framework in question is a framework-packaged version of Taglib taken from the Max source tree. The file that I tried to include was <taglib/mp4.tag> and compiling the .mm file that includes it always fail due to mp4tag.h is including <tag.h> without the <taglib/...> prefix in the include directive. The error is not only in this one header files, but there are similar issues in a large number of header files and thus modifying all of these include statements is non trivial. All of the required "missing" header files are actually present in the framework's Header subdirectory.

I'm trying to use Taglib in my app and although I was able to compile Taglib as a framework with header files and add it to my app, I can't seem to get the app to compile due to the issues above.

Anybody has any pointers?

Thanks.

It sounds to me like there is a bug with the framework - it should be using the same prefixes for its #import statements that it expects users of the framework to use. — Carl Norum
– Carl Norum, Commented Jun 26, 2010 at 16:24
This framework is not Mac OS X specific and they are C/C++ sources (no Objective-C source code in the framework). — adib
– adib, Commented Jun 27, 2010 at 16:59

JWWalker · Accepted Answer · 2010-06-26 16:36:09Z

1

I think that File1.h should say:

#include "File2.h"

Try checking the "Always Search User Paths" option in Xcode.

answered Jun 26, 2010 at 16:36

JWWalker

22.8k6 gold badges61 silver badges80 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

adib Over a year ago

The "Always Search User Paths" is checked (this is the default option). File1.h is part of the open source library and its not just one file (i.e. there are many header files that includes other header files in the library the same way).

JWWalker Over a year ago

OK, at this point I'm sure that the framework is set up incorrectly. If you can't fix it, then you'll need to add a header search path to the Headers folder of the framework.

adib Over a year ago

How can I tell whether the framework is set up correctly or not?

JWWalker Over a year ago

I meant that if it's including its own headers as if they were system headers (in angle brackets), that's incorrect.

jgb · Accepted Answer · 2013-10-10 05:14:04Z

0

Here are the steps to fix it:

Change the code to in File1.h to use '#include '.
In the framework project/default target/build phases, set the "copy files" phase and add both File1.h and File2.h.
Make sure that the "copy files" phase is before "compile" phase.

This should fix the issue, as the framework will refer to the files exactly the same way as the code that uses the framework.

edited Oct 10, 2013 at 5:14

jgb

1,2045 gold badges18 silver badges28 bronze badges

answered Oct 10, 2013 at 4:50

Boris Vidolov

1498 bronze badges

Collectives™ on Stack Overflow

A framework header cannot find its own header files in Xcode?

2 Answers 2

4 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related