From: Robert Ramey (ramey_at_[hidden])
Date: 2007-11-12 11:27:48
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:
Jamfile // testing bjam build and test
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
Rene Rivera wrote:
> Boris Gubenko wrote:
>> As this thread shows, people are running into this problem over and
>> over again. Because of this problem, I myself have to use prebuilt
>> bjam on HP-UX_ia64_gcc.
>> I think a patch for tools/jam/src/build.jam in
>> should be committed to trunk and made part of 1.35. It is confirmed
>> that the patch eliminates bjam crash. Once the problem in bjam
>> causing the crash is fixed, this workaround can be removed.
>> Since I was the one who submitted this patch, a usual question: Ok
>> to commit?
> Sure... Although making it into 1.35.0 is a different question. We'd
> need to do a bjam release for that.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk