From: Stefan Seefeld (seefeld_at_[hidden])
Date: 2003-11-19 10:58:09
Vladimir Prus wrote:
> Stefan Seefeld wrote:
>>Indeed, tracking source dependencies is not in the scope of qmtest.
>>However, since you can 'qmtest run my.test.in.a suite', it's easy enough
>>to hook it it up with everyone's preferred build system. (I wrote my
>>test database implementation to integrate with the make/autoconf based
>>build system, and I'm sure doing a similar thing for bjam is equally
> You know, there's one problem. If you run 'bjam' once for each test, it can
> be slow in itself. At least for me, running 'bjam' in status directory
> takes about 40 seconds, no matter if I request specific target -- with
> Boost.Build v1. V2 might behave better, but still... I'm not sure if that
> won't be too slow.
Hmm, I don't know bjam very well, so I may be missing something here.
I'd guess the time is spent mostly for constructing the dependency
graph. I didn't mean to suggest that bjam has to be invoked multiple
times. I'm sure bjam has its own idea of a 'task' / 'rule' or however it
is called. All that would be needed is a definition of a task that
invokes qmtest for a particular test, which then is invoked whenever
bjam decides that its time to run it again.
Anyways, my whole point is to show that even though qmtest itself
doesn't manage dependencies, it's easy enough to hook it up with
tools that are designed to do just that.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk