Boost logo

Boost-Build :

Subject: Re: [Boost-build] How to run inspect as part of a test-suite?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2013-12-26 08:47:44


On Thu, Dec 26, 2013 at 5:59 AM, Paul A. Bristow <pbristow_at_[hidden]>wrote:

>
>
>
>
> *From:* Beman Dawes [mailto:bdawes_at_[hidden]]
> *Sent:* Tuesday, December 24, 2013 8:56 PM
> *To:* steven; Boost.Build developer's and user's list
> *Subject:* Re: [Boost-build] How to run inspect as part of a test-suite?
>
>
>
> On Fri, Dec 20, 2013 at 11:17 AM, Steven Watanabe <watanabesj_at_[hidden]>
> wrote:
>
> AMDG
>
>
> On 12/20/2013 08:03 AM, Beman Dawes wrote:
> > On Fri, Dec 20, 2013 at 10:43 AM, Steven Watanabe <watanabesj_at_[hidden]
> >wrote:
> >
>
> >> 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:
> >>>
>
> >>> [ run /boost/tools/inspect//inspect/<variant>release
> >>> : .. -text -brief # command line
> >>
> >> You just need to root .. by using path-constant.
> >>
> >
> > Sorry, that's way above my bjam skill level. And since use of inspect in
> > this context is almost always going to need command line arguments, the
> ..
> > doesn't appear to be a problem.
> >
>
> What I mean is that passing a literal .. won't work
> when bjam is run from a different directory
> (status/ for instance).
>
> path-constant parent : .. ;
> # ...
> run ... : $(parent) -text -brief ;
>
>
>
> I've now tested this and it worked fine, AFAICS.
>
> All changes to inspect, timer, and the super have been merged to master.
>
Actually, I didn't push the timer changes to master until a few minutes
ago.

> This is a Really Useful Thing.
>
I'm hoping so.

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
     ]

Happy New Year,

--Beman



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