Re: autolink doesn't work when not specifyingtoolset version

Vladimir Prus wrote:
> Assuming the concrete proposal is:
>
> Whenever no explicit version of msvc is provided,
> run compiler, extract version from the output, and
> use that.
>
> and I'm asked to implement that in code, it would
require
> access to all versions of msvc for which that
behaviour
> is desired, plus a couple of days.

Personally, I'd rather we take a few days to fix this,
rather than ship "as 
is".

Vladimir: if there's anything I can do to aid testing of any
changes then 
let me know.

I believe that if we have "using msvc ;" in
user-config.jam then it 
automatically detects the available versions and sets the
most recent as the 
default?  Can we rig it so that --toolset=msvc has the same
effect?

The only issue is what happens if the user invokes bjam from
within an msvc 
command prompt.  Should we expect --toolset=msvc to invoke
the compiler 
that's currently in the path and detect it's version
correctly?  My gut 
feeling is this may be too much to ask for, but if so we
should say so in 
the docs (Dave?).

Regards, John.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

John Maddock wrote:

> Vladimir Prus wrote:
>> Assuming the concrete proposal is:
>>
>> Whenever no explicit version of msvc is provided,
>> run compiler, extract version from the output, and
>> use that.
>>
>> and I'm asked to implement that in code, it would
require
>> access to all versions of msvc for which that
behaviour
>> is desired, plus a couple of days.
> 
> Personally, I'd rather we take a few days to fix this,
rather than ship
> "as is".
> 
> Vladimir: if there's anything I can do to aid testing
of any changes then
> let me know.
> 
> I believe that if we have "using msvc ;" in
user-config.jam then it
> automatically detects the available versions and sets
the most recent as
> the
> default?  

I don't think that's happening.

> Can we rig it so that --toolset=msvc has the same
effect? 

--toolset=msvc has the same effect as "using msvc ;
"

Actually, I have an update. On IRC, Rene came up with a
one-line patch
that probably works in cases where msvc is installed in
standard location.
The patch is:

        http://rafb.net/p/1pC
k6V21.html

can you probably try it? Rene's asleep, and there's no way
I'll have
access to msvc today.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build