$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-11-12 11:58:10
Robert Ramey wrote:
> Is there a reason that bjam and the rest of boost build can't be handled as
> any other library as regards to testing and release?
> 
> Specifically, I would like to see somethiing like:
> 
> libs/bjam
>     /build
>        Jamfile
>     /test
>         Jamfile // testing bjam build and test
>         compile-fail.cpp
>         assert-fail.cpp
>         ...
> 
> So that bjam is automatically tested on all platforms when ever its changed.
> Of course this test/build would be run using the "released bjam" which
> would be updated when show stopping bugs are fixed and after the
> fixed version has been tested.
> 
> It might also provide a place to test tool configuraiton files and the like
I don't understand what you are asking. The current testing uses a 
"frozen" version of bjam with the understanding that we want testing 
tools to be as stable as possible.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo