From: David Abrahams (dave_at_[hidden])
Date: 2004-06-09 06:39:41
Vladimir Prus <ghost_at_[hidden]> writes:
> David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> > I'd like to finally settle the question that Michael raised some time
>> > ago. Briefly, given
>> > using gcc ;
>> > using gcc : 3.3 : g++-3.3 ;
>> > it is not clear if default-configured gcc is the same as gcc 3.3, or not.
>> > This might cause a problem for user, since he can build the project twice
>> > without need, and it causes some complexity for toolsets.
>> > Here's what I propose: each "configuration parameter" of toolset should
>> > be either specified on all calls of the "using" rule, or omitted in all
>> > the calls. The rationale is: first time user can invoke "using gcc ; "
>> > and it will work. Advanced user, who wants to configure several version,
>> > probably knows the version number of default "gcc" as well, so it's no
>> > problem for him.
>> I think we could get into trouble with separate "using" statements in
>> site_config / user_config. Don't forget that site_config may be
>> installed by some sysadmin somewhere.
> Then I wonder what could be done? Maybe, just a policy that shared site_config
> may not use versionless init.
I don't have specifics in mind, but I have the feeling we just need a
way to give people a little bit more explicit control: "I don't care
what you saw before; 'gcc' now means gcc-3.4"
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
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