Updated library_status for easier use..
Following up on the reorganization of the regression tools.. I'm happy to say that part of the changes I pushed last night include a cleaned up and easier to use library_status tool. Key changes, from the older version and the one Robert forked, are: * Processing the jam log (i.e. process_jam_log) is integrated into it. * Running b2 to build/run tests is also integrated into it (optionally). Which means that there's no external support script(s) needed and that it's fully cross-platform single executable. Documentation is updated at < https://rawgit.com/boostorg/regression/develop/index.html> on how to build it and on using it at < https://rawgit.com/boostorg/regression/develop/library_status/doc/library_st...
.
Obviously improvements from others welcome (as PRs). HTH -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
why not place this at the same level of all the other "tools" in the boost_root/tools/library_status. Then the layout, docs etc would look like all the other tools. wouldn't that be simpler? The you could give me ownership of this particular tool. I'm still unclear where process_log_log was supposed to end up when the "regression" directory was eliminated. And off topic, it's unclear why changes were made in the master branch but not in develop. This has created a lot of confusion. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/Updated-library-status-for-easier-use-tp4... Sent from the Boost - Dev mailing list archive at Nabble.com.
On 4/29/2015 1:01 PM, Robert Ramey wrote:
why not place this at the same level of all the other "tools" in the boost_root/tools/library_status. Then the layout, docs etc would look like all the other tools. wouldn't that be simpler? The you could give me ownership of this particular tool.
I'm still unclear where process_log_log was supposed to end up when the "regression" directory was eliminated.
And off topic, it's unclear why changes were made in the master branch but not in develop. This has created a lot of confusion.
There is no 'master' branch in the regression repository. Are you referring to some other repository ?
participants (3)
-
Edward Diener -
Rene Rivera -
Robert Ramey