[Boost-build] ambiguity in requirements

From: Artem Alimarine (artem_at_[hidden])
Date: 2006-07-17 15:36:19

My project has now a contruction like

project hello
    : requirements
      <link>static
      <threading>multi
    ;

lib hello_lib : hello_gcc.cpp : <toolset>gcc ;
lib hello_lib : hello_msvc.cpp : <toolset>msvc ;

I get the following error under cygwin
error: No best alternative for ./hello
    next alternative: required properties: <link>static <threading>multi 
<toolset>gcc
        not matched
    next alternative: required properties: <link>static <threading>multi 
<toolset>msvc
        not matched

The compiler command does is bjam --v2 hello

As far as I understand the build request has more targets than allowed 
by the project. For those targets, like
a shared single-threaded gcc build, there is no most specific rule.

How do I say to the build system that the only interesting builds would 
be static multithreaded gcc and msvc. I understand that it could be 
specified in the command line, but that is not a nice solution to give 
the arguments all the time.

Artem