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

From: David Abrahams (dave_at_[hidden])
Date: 2006-01-30 14:39:53

Vladimir Prus <ghost_at_[hidden]> writes:

> If we're to try move C++ Boost to V2, then should we implement 
> autoconfiguration for toolset, and in what form?
>
>
> Now, if you run "bjam --v2" on a fresh checkout you get a message that no 
> toolsets are configured. There are two ways around this:
>
> 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]

      ... 

      Boost.Build detected the following tools: 

        msvc-7.1        (Microsoft Visual C++)
        borland-5.6.4   (Borland C++ Builder)
        gcc-3.4.2       (Cygwin GCC)
        python-2.4      (Python interpreter)

      Which compiler would you like to use as your default compiler? [msvc-7.1]

      Configuration file generated: C:\Documents And Settings\dave\user-config.jam

*** HOWEVER ***

If we have the slightest shred of a hope of making the transition
before the upcoming release, we should -not- try to do this right
now.  It's great functionality to have, but it's not present in v1 and
so should not be required for making this transition.

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