From 9011d43fb3e3e8e7e6ff3b74f97e5d8aeb94c82f Mon Sep 17 00:00:00 2001 From: Peter Marheine Date: Mon, 8 Jan 2018 16:13:34 +1100 Subject: [PATCH] Recover discussion of -vv for build output First added in 723945cb0eae7d642caa88812c6ecee3ed5895a1 which failed to update the book and was replaced in 1271bb4de0c0e0a085be239c2418af9c673ffc87. --- src/doc/src/reference/build-scripts.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/doc/src/reference/build-scripts.md b/src/doc/src/reference/build-scripts.md index a50f3afea..42113a1ff 100644 --- a/src/doc/src/reference/build-scripts.md +++ b/src/doc/src/reference/build-scripts.md @@ -47,8 +47,10 @@ the source directory of the build script’s package. All the lines printed to stdout by a build script are written to a file like `target/debug/build//output` (the precise location may depend on your -configuration). Any line that starts with `cargo:` is interpreted directly by -Cargo. This line must be of the form `cargo:key=value`, like the examples below: +configuration). If you would like to see such output directly in your terminal, +invoke cargo as 'very verbose' with the `-vv` flag. Any line that starts with +`cargo:` is interpreted directly by Cargo. This line must be of the form +`cargo:key=value`, like the examples below: ```shell # specially recognized by Cargo -- 2.30.2