Re: [Boost-build] V2 transition and toolset autoconfiguration

From: David Abrahams (dave_at_[hidden])
Date: 2006-02-02 10:11:27

Vladimir Prus <ghost_at_[hidden]> writes:

> On Monday 30 January 2006 22:39, David Abrahams wrote:
>
>> > 1. Add
>> >
>> >           using gcc : auto ;
>> >           using msvc : auto ;
>> >
>> > to user config that will configure all toolsets there are, but don't
>> > complain if some toolsets don't exist.
>> >
>> > 2. Arrange for "bjam --v2 toolset=whatever" to try automatically loading
>> > toolset "whatever" and issuing
>> >
>> >     using whatever ;
>> >
>> > This, however, still requires user to provide the name of toolset.
>> >
>> >
>> > Any options?
>>
>>   3. "You have no configuration file.  Do you want Boost.Build to try to
>> detect the tools you have installed and generate a configuration file?
>> [Y/n]
>
> But in V1, "-sTOOLS=borland" works without writing any configuration file, so 
> we'll regress a bit in user-frienliness.

This is a good point.  I agree that we need to support #2.  Writing
xxx-config.jam files needs to be completely optional for the user
who's got things installed in the usual places.  So really, if you
don't specify a toolset and you don't have a configuration file, it
should try to find one and use that.  Similarly for BoostBook, Python,
etc.

I'd be happy to work on this in earnest if anyone wants to
cooperate... finding the time will be... interesting ;^)

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com