Re: [Boost-build] Replacement for --preserve-test-targets option

Subject: Re: [Boost-build] Replacement for --preserve-test-targets option
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-01-21 14:06:18

On Wednesday 21 January 2009 21:58:48 Jeremiah Willcock wrote:
> On Wed, 21 Jan 2009, Vladimir Prus wrote:
> 
> > On Wednesday 21 January 2009 19:35:19 Jeremiah Willcock wrote:
> >> I notice from
> >> <URL:http://www.nabble.com/Idiom-for-running-tests-using-(non-test)-target--td20135471.html>
> >> that the --preserve-test-targets command line option to bjam (mentioned in
> >> the documentation) has been removed and replaced by a feature settable
> >> from the Jamfile.  Is there still a way to set that flag from the command
> >> line?  Trying the original command line option does not work.
> >
> > Any feature can be requested on the command line. Did you try
> >
> > 	bjam preserve-test-targets=on
> 
> No, I hadn't.  I tried to look for documentation on how to turn features 
> on using the command line, and was not able to find that out.

Does:

        http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html

fail to explain this, or is "Invocation" section in TOC fails to suggest it
will tell how to specify things on the command line? Do you have any ideas
how to make this more discoverable?

> >> Also, the
> >> documentation should probably be updated to reflect the removal of that
> >> option.
> >
> > Which documentation? I think that the option was never documented.
> 
> Page 33 of <URL:http://www.boost.org/doc/tools/build/doc/userman.pdf>, 

Oh, you right. I'll fix that.

> for  
> example.  When I searched to find out how to keep the executables around, 
> many of the posts suggested that option.  Is there a timeline for making 
> that the default, as was mentioned in the earlier post?

No timeline, I presume right after 1.38.

- Volodya