Re: [jamboost] re: Darwin BBv2 CVS library suffix bug

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-28 01:55:02

On Tuesday 28 June 2005 10:43, Mat Marcus wrote:
> --On Tuesday, June 28, 2005 10:11 AM +0400 Vladimir Prus <ghost_at_[hidden]>
> wrote:
> [snip]
>
> > Typically, you can use target alternatives:
> >
> > alias boost_filesystem : /boost/filesystem ;
> > alias boost_filesystem : : <toolset>yfc ;
> >
> > When toolset=yfc, the second alternative will be selected, and... do
> > absolutely nothing.
>
> When the yfc is not enabled on a given platform, this causes an error
> (unknown toolset, with bbv2 1.32.0). 

This was a long-standing issue that's now fixed in CVS. You no longer need to 
declare a toolset to use <toolset>yfc in requirements.

> When the toolset is defined, I get 
> another error:failed to build ./boost_filesystem with properties because no
> best-matching alternative could be found. Maybe the behavior is different
> in a newer version?

Here's a complete example I've tested with:

alias fs : /home/ghost/Work/boost-rc/libs/filesystem/build ;
alias fs : : <toolset>intel ;
alias fs : : <toolset>foobar ;

exe hello : hello.cpp fs ;

(also can be found at http://zigzag.cs.msu.su/~ghost/alternatives)

Building with "gcc" links to boost.fs, and building with "intel" does not. 
This is with current CVS.

HTH,
Volodya

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