|
Boost-Build : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2002-07-11 13:51:16
At 10:26 PM 7/10/2002, David Abrahams wrote:
>> How about invoking Jam multiple times?
>>
>> invoke jam to build library X
>> add the results to the status table
>> repeat for libraries Y, Z, ...
>> invoke jam to run tests
>> add those results to the status table
>
>Try it and see if it works, I guess.
>
>> Note that <lib> dependencies have to be removed from the current
>> boost-root/status/Jamfile, since we just want the tests to fail if a
>> library isn't present. We don't want to try to build the library while
>> processing the status/Jamfile.
>
>??
>
>How do you propose to test the regex library, for example, if you don't
>arrange for it to be built?
That's step one - invoking bjam from the boost-root, so it builds libraries
as called for in boost-root/Jamfile.
I've just tested it, and you do get the compiler messages when one of the
compiles fails, so I guess we can live with that.
>Or, how do you propose to arrange for it to be built and linked into the
>executables?
Hum... I assumed that linking, but without forcing a build if the library
wasn't there, was doable. But I gather from other postings that this is
one of those things that will have to wait until version 2.
I'm sorry. It never occurred to me that jam would not be able to link to a
library that it had built in a prior job step.
Does that mean that until version 2 we should not report status on any
regression test that uses libraries? Or just report "It failed for unknown
reasons". Depressing.
--Beman
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