From 16e4c29587e9a0fb7e2d2ded6759fb5a8e5e6785 Mon Sep 17 00:00:00 2001 From: Sven-Hendrik Haase Date: Fri, 27 May 2022 12:25:10 +0200 Subject: [PATCH] Document how to debug change detection events This merely links to the FAQ which already explains this topic very well. --- src/doc/src/reference/build-scripts.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/doc/src/reference/build-scripts.md b/src/doc/src/reference/build-scripts.md index b4508ac9028..f4df9cb7f82 100644 --- a/src/doc/src/reference/build-scripts.md +++ b/src/doc/src/reference/build-scripts.md @@ -328,7 +328,9 @@ list of files controlled by the [`exclude` and `include` fields]). For most cases, this is not a good choice, so it is recommended that every build script emit at least one of the `rerun-if` instructions (described below). If these are emitted, then Cargo will only re-run the script if the given value has -changed. +changed. If Cargo is re-running the build scripts of your own crate or a +dependency and you don't know why, see ["Why is Cargo rebuilding my code?" in the +FAQ](../faq.md#why-is-cargo-rebuilding-my-code). [`exclude` and `include` fields]: manifest.md#the-exclude-and-include-fields