Re: autolink doesn't work when not specifyingtoolset version

Hi,

If this is a showstopper we better figure out what we do
about it. My  
question is who is doing what and when?

Any help with this issue will be greatly appreciated.

Thanks

Thomas


On May 7, 2007, at 12:37 PM, David Abrahams wrote:

> The following message is a courtesy copy of an article
> that has been posted to gmane.comp.lib.boost.user as
well.
>
>
> on Sun May 06 2007, "John Maddock"
<john-AT-johnmaddock.co.uk> wrote:
>
>> I don't think there's anything that autolinking can
do to fix this:
>> it requires that libraries are named consistently,
and there's no
>> way around that.
>
> Yes, that's not what I meant to imply.
>
>> So we either need to update the docs, or preferably
fix  
>> Boost.Build to
>> detect the MSVC version.  As Dave says it does this
in other contexts
>> already, so it should be possible.
>
> Exactly.
>
>> BTW, this is a showstopper for 1.34 release I
believe.
>
> Absolutely.
>
> -- 
> Dave Abrahams
> Boost Consulting
> http://www.boost-cons
ulting.com
>
> Don't Miss BoostCon 2007! ==> http://www.boostcon.com

-- 
Thomas Witt
wittacm.org



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

on Mon May 07 2007, Thomas Witt <witt-AT-acm.org>
wrote:

> Hi,
>
> If this is a showstopper we better figure out what we
do about
> it. My question is who is doing what and when?

I think Volodya should fix it, since only he understands
most of the
code in msvc.jam, and, I guess, right away, since we want to
ship 1.34


-- 
Dave Abrahams
Boost Consulting
http://www.boost-cons
ulting.com

Don't Miss BoostCon 2007! ==> http://www.boostcon.com

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

On Tuesday 08 May 2007 03:49, Thomas Witt wrote:
> 
> Hi,
> 
> If this is a showstopper

I suppose that you, as release manager, get to to decide of
this "if".
Calling "showstopper" something that does not
prevent getting working
binaries is a bit liberal as far as I'm concerned.

> we better figure out what we do about it. 

Apparently, no concrete proposal was made.

> My    
> question is who is doing what and when?

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.

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