|
|
Boost Testing : |
From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2006-03-21 10:13:39
Vladimir Prus writes:
> 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?
Yes, that was the motivation.
-- Aleksey Gurtovoy MetaCommunications Engineering