Re: [jamboost] xx-config.jam

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-05-23 01:05:26

On Monday 23 May 2005 07:39, Rene Rivera wrote:
> David Abrahams wrote:
> > These things are great!!
>
> Thank you :-)
>
> > Now, we should really unify them with "using."
> >
> > So,
> >
> > using msvc ;
> >
> > should essentially do
> >
> > import msvc-config ;
>
> That was my intent.. Never got an answer from Volodya about separating
> the toolset detection and config from the toolset operation.

Yea, sorry. IIRC, we basically agreed that 'using msvc' should try to
detect msvc and if found, initialize it. That's what Dave suggests above 
and it's what 'using msvc' does at the moment ;-), except that:
1. It issues a warning if msvc is not found.
2. The detection logic in msvc.jam and msvc-config.jam is different.

I think to move further we need to agree that the only two questions are:
1. Which detection logic is best
2. Whether we should have one file, that includes the detection logic,
or a separate xx-config with detection logic.

Do we agree?

> > of course we need to get msvc-config.jam to handle vc6.
>
> If I had it I could figure it out... Although it's really just a matter
> of knowing how it sets up the registry when installed.
>
> > Also, versions should be registered highest-to-lowest, and we should
> > implement the ability to do a versionless build, which should pick the
> > first version registered. So if 8.0 is installed,
> >
> > bjam msvc
> >
> > should be equivalent to
> >
> > bjam msvc-8.0
> >
> > Thoughts?
>
> I'm all for that.

I think that if 'using msvc' with detect/register 8.0 first, then

bjam msvc

will be the same as

bjam msvc-8.0

by using default properties, automatically. There are some details:

* does 'using msvc' initializes all found msvc version? Or only one?
* what if user issues explicit 'using msvc : 8.0 ....... ' after 8.0
is already initialized

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2