Subject: Re: [boost] what happened to the "tools/regression" directory - and the stuff in it?
From: Robert Ramey (ramey_at_[hidden])
Date: 2015-03-18 17:52:02
Rene Rivera-2 wrote
> Also, note that the code for that tool is now at <
> https://github.com/boostorg/regression/tree/develop/library_status>. And
> IIRC it's updated to build if you clone/get the regression repo. But I
> never tried using the resulting executable. And process_jam_log is at <
> Obviously something equivalent to this is necessary for every library
>> author. What do other library authors use? What do you recommend for
>> testing on one's own machine?
> Like Steven I just use b2 directly and read the output. But then I have a
> very simple library to deal with. So I'm not a good example.
In my source tree there was a folder icon named regression and I just
clicked it and the folder appeared in the right place in my modular-boost
tree. Which I suppose is OK - except that there's another corner of git
that I have to figure out how to use - this is a burden to me.
When I first saw this I presumed that the boost test python scripts had been
enhanced to provide this sort of facility in one's local environment. Now
I'm poking around to see how all this works. There is a directory with 15K
lines of *.py code it !!!
-- View this message in context: http://boost.2283326.n4.nabble.com/what-happened-to-the-tools-regression-directory-and-the-stuff-in-it-tp4673387p4673404.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk