From: David Abrahams (dave_at_[hidden])
Date: 2005-05-26 17:15:02
"Jeff Flinn" <TriumphSprint2000_at_[hidden]> writes:
>> If we skip Boost.Python we *do* need to tell people what they need to
>> set up in order to not get it to be skipped. Maybe you don't care,
>> but I do. I was the one fielding all the "Can't build Boost.Python"
>> questions before I had that big message.
> The summary could be after the existing output(including the current
> Boost.Python warning). It would give equal prominence to all three
> categories. One could then scroll up to see the specifics.
Oh. That's not bad. But hard to do with bjam as currently defined.
The last thing it does is update the big target dependency graph, so
the output would have to be the build action for a target, and it's
basically impossible to control the build order of targets unless they
have a dependency relationship.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk