Subject: Re: [Boost-build] help with v2 build system
From: Jonathan Brannan (kickace_at_[hidden])
Date: 2008-12-03 11:40:58
oh, nice! it does most of what I need.
I need a rule to fire off before testing.capture-output and I also
need the "generate-xml" rule to go off before RmTemps happens (I guess
I could just disable deleting of the test executables for testcov mode
if it comes to it).
I also have one test that has to link to extra libs when it's linking
shared, so it looks something like
run-test mytest : files files files : : : <link>static ;
run-test mytest : files files files extra libs : : : <link>shared ;
This seems to confuse the rules ("next alternative: required
On 12/2/08, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> Jonathan Brannan wrote:
>> I'm working to upgrade our boost and our current buildsystem/Jamrules.
>> I'm stuck trying to figure out how to do one of our test coverage
>> rules. In simple terms we do this:
>> before all tests arerun, execute an action (initialize)
>> before each test, execute an action specific to that test (zero out)
>> after each test is run, execute another action specific to that test
>> (gather stats from that output stats)
>> after all tests are run, execute an action (generate html)
>> I also want to assure that in the testcov build mode, unit tests are
>> always run regardless of changes.
>> I have figured out how to create a new variant of testcov and set the
>> proper cxxflags/cflags/ldflags, but I can't figure out the new
>> dependency/generation/type chaining.
> Does the attached Jamfile work?
> In Christ,
> Steven Watanabe
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