Header paths whose names don't match the #include directory name?
Header paths whose names don't match the #include directory name?
- Subject: Header paths whose names don't match the #include directory name?
- From: Jens Alfke <email@hidden>
- Date: Wed, 30 Oct 2013 13:01:54 -0700
Is there a way to configure header paths so that an include of the form “#include <dir/file.h>” will be found even if file.h’s parent directory isn’t actually called “dir”?
I ask because there are some projects whose source layout doesn’t match the way the built products are laid out, and the public headers #include each other according to the build layout. If you’ve checked out such a repository as a git submodule, and want to build it as part of your project without going through its whole build process, this becomes a problem.
Case in point: I’m trying to use YAJL <http://lloyd.github.io/yajl/>. I added it to my repository as a submodule and added the source files to my Xcode project. But they won’t build because the public headers are in yajl/src/api/, but they include each other as <yajl/___.h>.
All I need is some directive saying that #include <yajl/*> should be looked up in vendor/yajl/src/api/. Does that exist?
(Yes, I can run ./configure and make from the command line, which will produce an output directory with the right layout. But I don’t want to add extra build steps, and I need Xcode to build the library because I need binaries for iOS and the simulator as well as Mac OS.)
—Jens
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden