• 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: Dimbulb Xcode include path question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dimbulb Xcode include path question


  • Subject: Re: Dimbulb Xcode include path question
  • From: "Blair M. Burtan" <email@hidden>
  • Date: Fri, 26 Oct 2007 08:50:22 -0700

Well, that didn't help...perhaps I wasn't clear enough.

Myfancylibrary isn't a compiled library or framework.  Just a bunch of
open-source code.  Trouble is that they have things laid out in many
subdirectories and the code is peppered with #includes that have this path
structure as well as being bracketed instead of quoted.

Let me rephrase:

#include <myfancysources/myfancysource.h>
#include <myfancysources/somemodule.h>

And throughout the source files of myfancysources there are similar
#includes to other files in other subdirectories.

Blair M. Burtan
Northern Lights Productions
www.northernlights3D.com



>
> <myfancylibrary/myfancylibrary.h> can be interpreted two ways:
>
> - a file called myfancylibrary.h in a directory called myfancylibrary.h in
> some directory that's in your Library Search Paths
> - a file called myfancylibrary.h in the Headers directory in the framework
> myfancylibrary.framework in some directory in your Frameworks Search Path
>
> Make sure that if it's the latter that Frameworks Search Paths include the
> paths of the folders containing the frameworks, not to the framework itself
> nor deep into it.  Also, such frameworks shouldn't be in per-configuration
> locations (i.e. if you see a path component of Debug or Release or Development
> or Deployment, you're not doing it right)
>
> The normal way to do this in Xcode is to have the project that builds
> myfancylibrary build it to a shared Objects directory (SYMROOT), and then any
> projects that you drag and drop that framework into that share that Objects
> directory will pick it up automatically, for each configuration.
>
> Chris
>



 _______________________________________________
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: 
 >Re: Dimbulb Xcode include path question (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: Xcode 3?
  • Next by Date: re: objective-C and GTK
  • Previous by thread: Re: Dimbulb Xcode include path question
  • Next by thread: Re: Dimbulb Xcode include path question
  • Index(es):
    • Date
    • Thread