Re: [Boost-build] [bbv2 test] explicit test-suite ?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-09-30 06:54:05

On Friday 29 September 2006 02:37, David Abrahams wrote:
> "Eric Niebler" <eric_at_[hidden]> writes:
> > Rene Rivera wrote:
> >> Eric Niebler wrote:
> >>> I'm writing a Jamfile.v2 for some tests. I have two test suites, like:
> >>>
> >>>    import testing ;
> >>>
> >>>    {
> >>>        test-suite blah : [ run stuff.cpp ] ;
> >>>    }
> >>>
> >>>    {
> >>>        test-suite blah-ext : [ run experimental.cpp ] ;
> >>>    }
> >>>
> >>> Now, I'd like only the blah test suite to run by default, and I want
> >>> blah-ext to run only if I explicitly request it. The BBv2 docs led me
> >>> to believe "explicit" would help me, and I believed it! Sadly, it seems
> >>> not to be the case. Regardless of where I put the "explicit blah-ext ;"
> >>> line, the blah-ext test suite always runs, whether I ask for it or not.
> >>>
> >>> What have I overlooked?
> >>
> >> Looking up the testing.jam code... "test-suite" isn't a target.
>
> Rene means to say that the first argument to the test-suite rule
> doesn't become the name of a target.

I suppose it was a mistake to make test-suite work like this. Instead, 
test-suite should define a new alias target, and inline target declrations, 
like declaration of 'stuff' in

   test-suite blah : [ run stuff.cpp ] 

should be marked explicit.

I'll implement this.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2