From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-03-09 10:28:47
Aleksey Gurtovoy wrote:
> David Abrahams writes:
>> Martin Wille <mw8329_at_[hidden]> writes:
>>>>>- the testing procedure is complex
>>>> Internally, yes. The main complexity and _the_ source of fragility
>>>> lies in "bjam results to XML" stage of processing. I'd say it's one of
>>>> the top 10 issues by solving which we can substantially simplify
>>>> everybody's life.
>>> I agree. This processing step has to deal with the build system (which
>>> in complex itself) and with different compiler output.
>> I've always thought that a design that gets information by processing
>> stdout from bjam would be fragile. Furthermore, it means we can't use
>> the -j option with bjam, which, even on uniprocessors, can speed up
>> builds considerably. The build system itself should be writing the
> Exactly. Is BoostBuild v2. going to give us that?
Depends what you mean by "going". It's not a planned feature yet. And I
think it's better to try to make V2 the official build system before adding
any more features to it. After that, something should be possible.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk