|
Boost-Build : |
Subject: Re: [Boost-build] How to run inspect as part of a test-suite?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-12-26 13:58:07
AMDG
On 12/26/2013 10:20 AM, Paul A. Bristow wrote:
>
> Please give it a try and report any problems. Once it is working smoothly, I'll post a note to the main list letting maintainers know how to use it. Basically, what you do is to update your test Jamfile.v2:
> * Before anything else, add:
>
> path-constant parent : .. ; # so that inspect will start in boost-root/libs/timer
> # when run from another directory, such as boost-root/status
> * In the test-suite section add:
>
> [ run /boost/tools/inspect//inspect/<variant>release
> : $(parent) -text -brief # command line
> : # input files
> : <dependency>/boost/filesystem//boost_filesystem
> <test-info>always_show_run_output # requirements
> : inspect # test name
> ]
> As usual, I am too stupid to get this to work L
> I've added this to end of my jamfile (there being no test-suite in my Quickbook building docs file).
You don't absolutely need a test-suite. You can just use
run ... ;
> test-suite "svg_plot"
> :
> [ run /boost/tools/inspect//inspect/<variant>release
> : $(parent) -text -brief # command line
> : # input files
> : <dependency>/boost/filesystem//boost_filesystem
> <test-info>always_show_run_output # requirements
> : inspect # test name
> ]
> ;
> but I get this:
> Jamfile.v2:250: in modules.load
> *** argument error
> * rule run ( sources + : args * : input-files * : requirements * : target-name ? : default-build * )
> * called with: ( : I:\boost-trunk\libs\svg_plot -text -brief : : <dependency>/boost/filesystem//boost_filesystem <test-info>always_show_run_output : inspect )
> * missing argument sources
This shouldn't be possible. What version of b2 are
you using, exactly? Is what you posted the /exact/
code that you tried? (i.e. no extra/missing special
characters, comments, spaces, &c.) The argument
"/boost/tools/inspect//inspect/<variant>release"
is somehow disappearing.
> <snip>
> I'm still not using GIT but existing last boost-trunk - is this cause of my trouble?
No. It will cause a different problem, though.
(No project called /boost/tools/inspect)
In Christ,
Steven Watanabe
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