Re: [Boost-build] Seleting alternatives based on multiple conditions

From: Daniel Einspanjer (deinspanjer_at_[hidden])
Date: 2006-03-10 15:06:22

"Emil Dotchevski" <emildotchevski_at_[hidden]> wrote in message 
news:BAY102-DAV4F43D93A055AFFA38DD1CD4ED0_at_phx.gbl...
>OK, I separated a simple test case completely outside of my source code
>tree. I believe the only thing that's used from my usual configuration is
>site-config.jam, with the following content:
>
>import toolset : using ;
>using msvc : 8.0 ;
>using msvc : 7.1 ;
>using gcc ;
>using como-win ;
>
>I simplified my test case to the point of only distinguishing between
>msvc-7.1 and msvc-8.0, that is, I don't have the additional alternatives 
>for
><release> or <debug>.
>
>So, in this isolated folder I have a single file, jamroot, with the
>following in it:
>
>lib a : : <toolset>msvc-7.1 <file>a1 ;
>lib a : : <toolset>msvc-8.0 <file>a2 ;
>exe b : a ;
>
>I launch bjam like so:
>
>bjam variant=release toolset=msvc-7.1 -n

One thing I notice is that it looks like you expect to be able to use gcc or 
como-win as toolsets, but you provide no alternative for them.  I believe at 
the very least, you should have an empty alias if those toolsets require no 
support lib a. Obviously, that wouldn't work properly in this testcase since 
exe b has no extra source files.

alias a ;
lib a : : <toolset>msvc-7.1 <file>a1 ;
lib a : : <toolset>msvc-8.0 <file>a2 ;

exe b : b.cpp a ;