[Cook] relative include

[Aaron Denney]

On Mon, Oct 14, 2002 at 08:33:00AM -0500, Jerry Pendergraft wrote:
> I would suggest/encourage putting the library source in the trunk of a
> project and then have your other two projects be branches under it.
> Much more simple. You have no such path issues *AND* you are not
> duplicating the library source, with the resulting possibility of getting
> out of sync.

This isn't actually the problem I want to solve, just an example of
where this might come in handy.  Even if it were, this just doesn't feel
like the right thing to do: the two (or three, or four...) projects
are not aspects of a single work, they just depend on a shared work.
The duplication need not be an issue, if you're using something like
perforce that can remap locations.

Quick hacks can do 90% of what I want (but will probably never support
things like [glob *.ext] the right way), so I suppose I'll try coding
one up and seeing how far I get.

-- 
Aaron Denney
-><-