My codebase is broken up into a little ecosystem of about 25 crates.
cargo prints a message each time it starts compiling a crate, but never prints anything when it finishes, even when
-vv is supplied. So oftentimes during a long build my console looks like this:
Compiling rayon-core v1.3.0 Compiling netlib-src v0.7.4 Compiling syn v0.12.14 Compiling serde_derive v1.0.18 Compiling indoc v0.2.3 Compiling enum-map v0.2.24 Compiling chrono v0.4.0 Compiling failure v0.1.1 Compiling rayon v0.8.2 Compiling frunk_derives v0.2.0 Compiling bindgen v0.31.3 Compiling rsp2-assert-close v0.1.0 (file:///home/lampam/cpp/other/rust/rsp2/src/util/assert-close) Compiling rsp2-soa-ops v0.1.0 (file:///home/lampam/cpp/other/rust/rsp2/src/util/soa-ops) Compiling vasp-poscar v0.1.1 (loooooooong pause)
and I actually have no idea which of the last 8 or so crates listed is the one that’s taking so long to compile. (all I know is that it can’t possibly be
vasp-poscar which takes 4 seconds to build on its own).
I mean, I guess I could just Ctrl-C it and re-issue the build command (in which case the culprit will be the first crate to appear), but it’d be nice if such information could come from cargo. (along with the time that each crate took)