<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Dec 19, 2013 at 10:54 AM, Vladimir Prus <span dir="ltr"><<a href="mailto:ghost@cs.msu.su" target="_blank">ghost@cs.msu.su</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 19.12.2013 19:13, Beman Dawes wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> The inspect program (<a href="https://github.com/boostorg/inspect" target="_blank">https://github.com/boostorg/<u></u>inspect</a>) does a nice job of detecting various library boo-boos, but the traditional use<br> (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<br> development and maintenance workflow.<br> <br> 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?<br> <br> 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<br> 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<br> check for change and rebuild if needed on a once per b2 invocation basis, not once for each library that uses inspect.<br> </blockquote> <br></div></div> Beman,<br> <br> the attached appear to almost work, except that inspect does not run in the current directory. Can you play with this one<br> before we go on fixing the remaining issue?<br></blockquote></div><br></div><div class="gmail_extra">Will do. <br><br></div><div class="gmail_extra">Thanks for the fast response.<br><br></div><div class="gmail_extra">--Beman<br> </div></div>