Re: [Boost-build] How to run inspect as part of a test-suite?

Subject: Re: [Boost-build] How to run inspect as part of a test-suite?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-12-20 10:43:39

AMDG

On 12/20/2013 07:10 AM, Beman Dawes wrote:
> On Thu, Dec 19, 2013 at 10:54 AM, Vladimir Prus <ghost_at_[hidden]> wrote:
> 
> Everything appears to work! See the develop branch of the super-project,
> inspect, and timer. (I used the timer library rather than filesystem for
> testing).
> 
> Inspect has been changed to take an optional first argument specifying the
> starting directory.  I've gotten the best results with
> 
>      [ run /boost/tools/inspect//inspect/<variant>release
>        : .. -text -brief # command line

You just need to root .. by using path-constant.

>        : # input files
>        : <dependency>/boost/filesystem//boost_filesystem
>          <test-info>always_show_run_output # requirements
>        : inspect # test name
>      ]
> 
> The only minor issue I've run into is that the only way I know to force a
> rerun is "b2 -a inspect", and that builds way more than desired. In
> general, is there a way to say "rerun just the specified test case?"
> 

In theory you could use -t targetname.  However,
to do that, you'd need to know the internal
name of the target.  I don't recall Boost.Build
having an option that operates on the main
targets.

In Christ,
Steven Watanabe