Build requirements bug?

On Tuesday 23 May 2006 22:13, Pedro Lamarão wrote:
> Attached is a small project containing a simple target
like this:
>
>   exe test
>
>     : main.cpp
>     : <toolset>msvc
>
>       <toolset-msvc:version>6.0
>     ;
>
> Calling bjam in the project folder like this:
>
>   bjam toolset=msvc-7.1
>
> actually builds said project... with msvc-6.0.

Given that you explicitly require version 6.0 in target
requirements, this is 
an expected result. If you want 6.0 to be default version,
you need to put 
that to default build:

   exe test 
       : main.cpp 
       : # no requirements
       : <toolset>msvc
         <toolset-msvc:version>6.0
       ;

HTH,
Volodya


-- 
Vladimir Prus
http://vladimir_pru
s.blogspot.com
Boost.Build V2: http://boost.org/boost-
build2
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus escreveu:

> Given that you explicitly require version 6.0 in target
requirements, this is 
> an expected result. If you want 6.0 to be default
version, you need to put 
> that to default build:
> 
>    exe test 
>        : main.cpp 
>        : # no requirements
>        : <toolset>msvc
>          <toolset-msvc:version>6.0
>        ;

Hum...
Shouldn't that bjam invocation fail?
My intention is not to make msvc-6.0 the default compiler,
but the only
compiler where this target builds.
It seems weird that I request toolset=msvc-7.1 on the
command line and
the target builds with another toolset.

--
 Pedro Lamarão

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