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: Paul A. Bristow (pbristow_at_[hidden])
Date: 2013-12-26 05:59:03

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.
This is a Really Useful Thing.
I've been running inspect.exe in a batch file after my document build, but this is much better and should reduce the number of broken links etc that are marring otherwise excellent documentation - you get immediate feedback while you are writing, whatever documentation tool you use.  (I've also used the 'warn of undocumented items' option in Doxygen and this has caught a number of mistakes and omissions so must be a Good Thing). 
Thanks
Paul
 
 
---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
[phone]  07714330204
pbristow_at_[hidden]