BBv1 strange behavior for requirement-rules

From: David Abrahams (dave_at_[hidden])
Date: 2003-08-15 12:32:42

Note the following which I'm adding to the codebase:

# Stick this rule name in your requirements if you are building code
# which requires locale support. It handles the metrowerks-specific
# case that locale support demands the static version of the runtime
# library.
rule std::locale-support ( toolset variant : subvariant-path properties * )
{
if [ MATCH .*(metrowerks|cwpro).* : $(toolset) ]
{
local p = [ MATCH (.*)runtime-link-dynamic(.*) : $(subvariant-path) ] ;

return
$(p[1])runtime-link-static$(p[2])
[ difference $(properties[2-]) : <runtime-link>dynamic ]
<runtime-link>static
;
}
else
{
return $(subvariant-path) $(properties) ;
}
}

The whole subvariant-path-split business is in there because the first
element passed is not a property, but the subvariant path in use (very
surprising!). I have to change it to correspond to the computed
properties. Shouldn't the subvariant path be computed *after* all
these rules are done modfying it?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com