Re: [Boost-build] alias/test-suite/inline targets changes

From: David Abrahams (dave_at_[hidden])
Date: 2006-11-04 20:15:32

Vladimir Prus <ghost_at_[hidden]> writes:

> I'm not quite sure about V1's behaviour where test-suites were explicit by 
> default. That differs from every other target.
>
> Also, IIRC, V1 has a special 'test' target that is not declared explicitly, 
> and which results in building all tests.  Again, I'm not sure it's good idea 
> to implicitly define taregts.

It may not be as important in v2, although if you want to aggregate
all the tests from subprojects, into one target, I don't see a better way.

> So, what do you think is the right behaviour to have in V2?

test suites will often want to be explicit.  In the common (non-boost)
case, people will put the test suites alongside their other main
targets in a single project, not separated by directory.  In general,

            bjam

shouldn't run a big test suite.  IMO.

Whether or not that makes it worth having all test suites be explicit
by default, I don't know.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com