Subject: Re: [Boost-build] How to run inspect as part of a test-suite?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-12-19 10:54:01
On 12/19/2013 07:13 AM, Beman Dawes wrote:
> The inspect program (https://github.com/boostorg/inspect) does a nice job
> of detecting various library boo-boos, but the traditional use (run report
> for all libs, post on a web site somewhere) is ineffective. No one looks at
> the report and it isn't a part of regular library development and
> maintenance workflow.
> Since inspect runs fine on an individual library, I'd like to add running
> it to the test-suite for libraries I maintain. How would I do this?
> If running inspect as part of my regular tests turned out to be helpful,
> many other libraries might follow suit and eventually we might even require
> it for all libraries. Thus while it would be useful if inspect was rebuilt
> whenever it or its dependencies change, we would want the check for change
> and rebuild if needed on a once per b2 invocation basis, not once for each
> library that uses inspect.
It would be a lot easier if inspect could
take a path to process instead of always
using the current working directory.
I think something like this should work, though:
use-project /boost/inspect : ../../../tools/inspect/build ;
path-constant dir-to-inspect : .. ;
: # args
: # input files
: # requirements
<testing.launcher>"cd \"$(dir-to-inspect)\" &&"
: # target name
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk