• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Header paths whose names don't match the #include directory name?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Header paths whose names don't match the #include directory name?


  • Subject: Re: Header paths whose names don't match the #include directory name?
  • From: Damian Carrillo <email@hidden>
  • Date: Wed, 30 Oct 2013 16:26:58 -0500

Sorry, I forgot to include the list. Here we go again...

How about symlinking from vendor/yajl/src/api to vendor/yajl/src/yajl, and then adding vendor/yajl/src to the Header Search path? It's a bit sloppy, but I can't recall any problems that I've run into doing that before. I'm fairly certain I've even done that with YAJL previously.

Sent from my iPhone

> On Oct 30, 2013, at 3:01 PM, Jens Alfke <email@hidden> wrote:
>
> 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

 _______________________________________________
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


References: 
 >Header paths whose names don't match the #include directory name? (From: Jens Alfke <email@hidden>)

  • Prev by Date: Header paths whose names don't match the #include directory name?
  • Next by Date: Re: Can't get IB to let me constrain to nearest neighbor
  • Previous by thread: Header paths whose names don't match the #include directory name?
  • Next by thread: Re: Can't get IB to let me constrain to nearest neighbor
  • Index(es):
    • Date
    • Thread