Re: How to suppress toolset in target paths?

From: David Abrahams (dave_at_[hidden])
Date: 2004-12-23 13:25:15

Vladimir Prus wrote:
> On Tuesday 14 December 2004 19:32, David Abrahams wrote:
> 
>> > Hmm... I was not aware of that, and you did not tell that in previous
>> > discussions.
>>
>> I'm surprised to hear that. It's been a basic feature of BBv1 since the
>> beginning.
> 
> Well, I'm surprised too :-O
> 
>> > I think such automatic detection is very well possible.
>> >
>> > There's one question though. In past, Jurgen said that at least for him
>> > it's better to have everyting built in separate directories. Say, if
>> > bison produces files to "bin", them "bjam --clean release" will clean
>> > those files too, and he did not like this.
>> >
>> > Do we need yet another option?
>>
>> I don't understand the case you're describing or what it has to do with
>> the discussion at hand. What kind of separation is desired, and how
>> will it prevent cleaning of certain files during bjam --clean release?
>> Specifics are needed.
> 
> I have /space/NM/boost which is shared between several folks (it's built once 
> in several configuration). Then I have /home/ghost/Work/nm_model which 
> uses /space/NM/boost. When running with --clean 
> in /home/ghost/Work/nm_model, /space/NM/boost is cleaned too.
> 
> Most of the time, it's not desired. When I do it, I just clean too much. When 
> other folks do it, they get "permission denied" messages.

My point is that (it seems to me) where things are placed and what will
get cleaned can and probably should be orthogonal questions.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com