Commands or tools for viewing build dependencies #2011
Comments
bors
added a commit
that referenced
this issue
Oct 6, 2015
This series of commits performs two primary tasks: * The backend is refactored (again!) to have a much better understanding of what's used as input to everything else in terms of parallelization and dependency tracking. The major goal here was to completely unify all parts of the backend which sort of ad-hoc track dependencies and deal with cross compilation. More details can be found in the first commit message. * Greatly improving diagnostics for why a crate is being rebuilt. This still requires setting `RUST_LOG`, but it was spurred on by #2011 and should help at least my own personal internal debugging of "why is this crate rebuilding?" which seems to come up quite often!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have two scenarios here that are tough for us on Servo today:
cargo buildinvocation (e.g., why is script rebuilding?)To date, we've used the fingerprint logging support, but that's somewhat awkward at best. It would be awesome to have some kinda of tool or debugging infra to make this better.
cc @pcwalton @metajack @glennw
The text was updated successfully, but these errors were encountered: