|
Boost : |
From: Andrew Maclean (a.maclean_at_[hidden])
Date: 2005-03-09 17:26:30
Maybe you want to look at what Kitware does; they use CMake as a
cross-platform generator, and Dart for testing. The process seems reasonably
automated. CMake is a cross-platform generator similar to bjam with the
advantage that it generates IDE's, it also handes testing fairly
automatically. It is also PC friendly (aside from being *nix and Mac
friendly). You guys could do wonders using CMake and Dart linked with Boost.
Look at:
http://www.vtk.org/Testing/Dashboard/20050309-0300-Nightly/Dashboard.html
for the dashboard and http://www.cmake.org/HTML/Index.html
Andrew
-----Original Message-----
From: Aleksey Gurtovoy [mailto:agurtovoy_at_[hidden]]
Sent: Wednesday, 9 March 2005 21:05
To: boost_at_[hidden]
Cc: boost-testing_at_[hidden]
Subject: [boost] Re: [1.33.0] Let's start preparations...
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
> XML.
Exactly. Is BoostBuild v2. going to give us that?
-- Aleksey Gurtovoy MetaCommunications Engineering
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk