• 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: Source Tree Preference
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Source Tree Preference


  • Subject: Re: Source Tree Preference
  • From: Benjohn <email@hidden>
  • Date: Mon, 10 Nov 2003 16:47:55 +0000

On 8 Nov 2003, at 17:14, Scott Tooker wrote:

Just to clarify some things:

1. Xcode doesn't support recursive search paths.

I'm (personally) not too bothered (so far, duno how it'll pan out though) about not having recursive search paths. Using Boost as an example, my includes would usually be of the style:
#include <boost/shared_ptr.hpp>
#include <boost/bind.hpp>
#include <boost/numeric/ublas/blas.hpp>
etc



2. The 'Source Trees' support provides a way for users to define custom root paths. For example, the CodeWarrior Importer defines a source tree that points to the "Metrowerks CodeWarrior" folder on your disk. This makes it possible to define a relative path to PowerPlant files that works for multiple users. Of course, this requires that each user define the same Source Tree name in their preferences.

Then source trees are an alias for a folder of source? Using an alias allows each developer to instal the folder at a location of their choosing.


Right :)

So the best thing to do in your case is create a source tree that points to the root of the boost sources. Then add all the boost sources (including the headers) to the project and use that source trees for the reference style (instead of project relative, make it point to your source tree).

*snip*

At this point you'll probably need to add header search paths as needed (though, since you've included all the headers you shouldn't need many).

Ok, so stuff that's part of the project, irrespective of where it is, can be included in the style:


	#include "thing_in_project.hpp"

Because our source files include boost in the manner I described above, am I correct that this wont work? I would have to modify as follows:
#include <boost/shared_ptr.hpp> -> #include "shared_ptr.hpp"


As I don't want to make a change like that, I can instead add boost's root to the include path using an the info inspector for the project.

However, I don't want to explicitly reference boost's local folder on my machine, do I? Presumably there is some syntax that makes use of the source tree name? Perhaps ...{BoostPath}... or ...$BoostPath... or something?


Cheers, Benjohn _______________________________________________ xcode-users mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Source Tree Preference
      • From: Scott Tooker <email@hidden>
References: 
 >Source Tree Preference (From: Benjohn Barnes <email@hidden>)
 >Re: Source Tree Preference (From: Scott Tooker <email@hidden>)

  • Prev by Date: RE: Kudos to the Xcode dev team
  • Next by Date: Re: Source Tree Preference
  • Previous by thread: Re: Source Tree Preference
  • Next by thread: Re: Source Tree Preference
  • Index(es):
    • Date
    • Thread