Boost logo

Boost-Build :

From: Peter Foley (pjfoley_at_[hidden])
Date: 2005-07-11 06:35:46


"David Abrahams" <dave_at_[hidden]> wrote in message
> Vladimir Prus <ghost_at_[hidden]> writes:
> > On Thursday 07 July 2005 17:35, David Abrahams wrote:
> >> Vladimir Prus <ghost_at_[hidden]> writes:
> >> > Either we need to decide that <include> should be treated relative
> >> > to source location, and not Jamfile location (no opinion yet),
> >>
> >> Until we get a clear definition of the term "source location," I'm
> >> strongly against it!
> >>
> >>
> >> After we get a definition, I'm probably still against it, but it's
> >> hard to say without knowing what it means. ;-)
> >
> > "source location" is a directory that all file references in Jamfile are

> > relative too.
> >
> > project : source-location foo ;
> >
> > exe a : a.cpp ;
> >
> > Here, 'a.cpp' is looked up in directory <Jamfile-dir>/foo
> >
> > Does this make it clear?
> Yes, thanks. In that case, I'm for it!

I am just wondering what the verdict was?

Is it ok to assume that all files are relative to an element in the source
location variable?

If this is the case is this a change that needs to be made in the wix.jam
file (this is the file that would normally sit in the "build/v2/tools"
directory [1]).

If it is not a change to the wix.jam file is that a source code change to



[1] - Just out of curiosity what do I actually call these files located in
this directory (build/v2/tools)? Do I call them "toolsets"? It is hard to
know what to call them since the majority of files have the "*.jam"


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at