Re: [jamboost] test-development merge plans?

From: Beman Dawes (bdawes_at_[hidden])
Date: 2002-03-02 17:09:36

At 05:43 PM 3/1/2002, David Abrahams wrote:

>> Thus I'm wondering if there is a plan to merge "test-development" 
anytime
>> soon?
>
>Already done. I sent you an announcement several days ago.

Thanks! I must have missed the announcement.

(Several minutes later...)

Great! A lot of the odd behavior I was seeing has disappeared. I added 
this regression test (to my working copy, which has branch 
unit_test_development installed):

run libs/test/example/unit_test_example1.cpp
libs/test/src/unit_test_main.cpp
<lib>../libs/test/build/boost_test ;

And it now works exactly as expected, kicking off the library build when 
needed. Thanks!

>> Unrelated issue: Why does boost-root/Jamfile "subinclude status ;"?
>Isn't
>> the resulting regression test something that is only of interest to
>> developers, and something that end-users wouldn't want to be bothered
>with?
>
>Yes. It's only so you can "jam test" from the top level, which I don't 
find
>to be compelling.

I don't find that compelling either. The top level Jamfile should just be 
stuff end-users would like to make happen as part of a very basic 
build. The regression test is expensive in time and disk space (at least 
on a limited machine). Anyone with interested can always run it via the 
status/Jamfile.

Unless someone has a strong counter argument, I think we should remove 
"subinclude status ;" Or make it conditional, so that it is there, but 
only invoked if the user specifically asks for it. I don't know how to do 
that, but I'm guessing it would be easy for a Jam expert:-) But it hardly 
seems worth the trouble.

--Beman