12 Oct
2005
12 Oct
'05
1:34 p.m.
"troy d. straszheim" <troy@resophonic.com> writes:
326.17s user 153.82s system 92% cpu 8:40.03 total
the first ~30 seconds of which is bjam calculating the dependencies for each test module.
Unless you have used bjam's profiling feature to break the execution time down carefully, you shouldn't draw any conclusions about how much time it spends calculating dependencies -- they're usually wrong. -- Dave Abrahams Boost Consulting www.boost-consulting.com