|
|
Boost Testing : |
From: Reece Dunn (msclrhd_at_[hidden])
Date: 2006-03-20 06:15:59
Vladimir Prus wrote:
> Martin Wille wrote:
> > Vladimir Prus wrote:
> >> Martin Wille wrote:
> >>
> >>>after some reverse-engineering I was able to make regression.py not
> >>>create another copy of the Boost tree. I also found out that
> >>>regression.py apparently ignores the BOOST_BUILD_PATH environment
> >>>variable and instead sets its own path (why?).
> >>
> >> Good question. I don't know, apparently is happened this way before.
> >> Would it be more convenient for you if this is fixed, by appending the
> >> current directory to the value of BOOST_BUILD_PATH from the environment?
> >
> > That would be sufficient. However, I don't understand why that script
> > should modify BOOST_BUILD_PATH at all if that variable is already set.
> > (The same could be said about BOOST_ROOT)
>
> No do I. Maybe, the idea is that custome toolsets can be added to this
> directory where regression.py is run?
I think this is so that if you already have a Boost install on the test machine with
BB(v2) already configured, the regression tests will use the correct version of
Boost (the one it downloads) and not your version which could be out of date.
- Reece
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/