Yes, that's the problem. There is another way:
rule format-rtlink ( toolset variant : properties* )
{
if [ MATCH .*(metrowerks).* : $(toolset) ] || [ MATCH .*(cwpro).* : $(toolset) ]
{
return <runtime-link>static $(properties) ;
}
else
{
return <runtime-link>dynamic $(properties) ;
}
}
Now add format-rtlink to the requirements.
this sounds perfect. I couldnt have come up with this myself . But I had planned to read the docs about bjam and Boost.Build in depth when V2 comes out, so one day, I'll know how to write advanced Jamfiles too ! :)
Unfortunately, I left home again and I'd have a hard time commiting changes to the boost cvs where I am now.
can you please make the changes to
$Boost/libs/format/tests/Jamfile and commit ?
oh, and while you're at it,
the ios_state regression tests need the same treatment, and I think they are launched via
$Boost/status/Jamfile.. ;-)
That would probably fix the 2 intel-linux-7.1 regressions and hopefully allow for 1.30.2 release..
best regards, -- Samuel
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
