From 8fc79674dc37f0a9f7c505fd34311c31e8f16747 Mon Sep 17 00:00:00 2001 From: bunnie Date: Thu, 20 Oct 2022 15:55:24 +0800 Subject: [PATCH] leave maintainer hints cargo debugging is so hard. If you're OK with it, I really would like gems like how to debug this code to be included as a comment in the source where you might look to fix such problems. Google turns up crap results when you try to search for these hints, and the results have been really unstable as well. I know such comments pollute the source code but it'll save a lot of time in the future trying to remember the trick to debug a tricky thing later on, I think. --- utralib/build.rs | 3 +++ 1 file changed, 3 insertions(+) diff --git a/utralib/build.rs b/utralib/build.rs index cfdd0850e..107174d6e 100644 --- a/utralib/build.rs +++ b/utralib/build.rs @@ -107,6 +107,9 @@ fn main() { // ----- control file generation and rebuild sequence ----- // check and see if the configuration has changed since the last build. This should be // passed by the build system (e.g. xtask) if the feature is used. + // + // Debug this using: + // $env:CARGO_LOG="cargo::core::compiler::fingerprint=info" #[cfg(not(feature = "hosted"))] { let svd_file_path = std::path::Path::new(&svd_filename);