From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-02-23 20:06:15
At 04:35 PM 2/23/2003, Rene Rivera wrote:
>Some organizational items... Here's a TODO list for Boost.Jam.
>* Add the timming output Beman wants for the basic build actions.
>- Difficulty: MEDIUM.
Timing breaks down into two components:
* Build (compile/link) timing.
* Run timing.
I don't see any way to get "build" timing without support from Boost.Jam.
But "run" timings can always be reported (to cout) by the program involved,
and then extracted by the post-bjam process. I think we missed that point
in prior discussions.
Now I'd certainly like to be able to report build timings, too, but it is a
medium or even low priority request.
Would it really be that hard anyhow? Couldn't you just wrap all applicable
build commands (c action, c++ action, link action, etc) with a call to a
timing program (which starts timer, calls system with the args ( being
the program to execute), reports timer, returns)?
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