Re: unable to have 2 prebuilt libraries with same leaf name in a project?

From: Reece Dunn (msclrhd_at_[hidden])
Date: 2005-10-13 08:03:39

"Kevin Wheatley" wrote
> I wondered why the following causes a problem:
>
> local mypath = somepath ;
> lib foo : : <file>$(mypath)/Release/foo.lib <variant>release ;
> lib foo : : <file>$(mypath)/Debug/foo.lib <variant>debug ;
>
> lib otherlib : [ glob *.cpp ] foo : <link>static ;
>
> bjam appears to complain about their being ambiguity "no best-matching
> alternative could be found"

This is because BBv2 cannot match a toolset with lib foo. You would need to
specify the <toolset> (and possibly the <os>) versions explicitly, e.g.:

<variant>debug/<toolset>msvc

or

<variant>debug/<toolset>msvc/<os>nt

Volodya/Dave - This is a common problem with users, so we should document it
in the tutorial/FAQ. The toolset is necessary because of the object format
and name mangling issues between compilers, so BBv2 is doing the right thing
here. We might also want to issue a more detailed error message.

HTH,
- Reece