From: Reece Dunn (msclrhd_at_[hidden])
Date: 2006-06-26 11:59:16
David Abrahams wrote:
> "Reece Dunn" <msclrhd_at_[hidden]> writes:
> > David Abrahams wrote:
> >> Isn't "$(BOOST_ROOT)" just supposed to be "boost"? Or am I missing
> >> something?
> > (2) You import the $(BOOST_ROOT) library names in a parent Jamfile
> > of the one you are referencing the boost//library in. I can't recall
> > exactly how to do this, but I think it is something like:
> > using-project boost : $(BOOST_ROOT) ;
> use-project boost : /path/to/boost/root ;
> > You could have:
> > alias boost : $(BOOST_ROOT) ;
> > and
> > exe test : [ glob *.cpp ] boost//thread ;
> > I believe that would work. Either way, I think you need
> > $(BOOST_ROOT) somewhere when you are not in a child of
> > $(BOOST_ROOT).
> I guess my point is that you don't really need $(BOOST_ROOT)
> anywhere. That variable was a requirement for BBv1 in some cases, but
> now it's obsolete... and yet, people cling to it.
I wasn't aware that $(BOOST_ROOT) was a V1 thing and that it is
One advantage to using BOOST_ROOT is that if you have a project
that is dependant on Boost checked into CVS, Perforce or some other
source control system in such a way that the project and Boost could
be anywhere on the system, if you want that project to use Boost,
BOOST_ROOT is the easiest way to avoid issues. If you check in to
use-project boost : c:/boost ;
then this prevents the developer(s) working on that project from
having Boost somewhere else (and prevents Unix/Mac development!)
I would say having:
use-project boost : $(BOOST_ROOT) ;
at the root of your project (or some other environment variable)
is the best you can do in this situation. I like being able to say:
etc. in BBv2.
Try Live.com - your fast, personalized homepage with all the things you care about in one place.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk