aboutsummaryrefslogtreecommitdiff
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorMiguel Ojeda <ojeda@kernel.org>2023-06-16 02:16:26 +0200
committerMiguel Ojeda <ojeda@kernel.org>2023-08-09 19:33:31 +0200
commite90db5521de2e00b63ba425b3b215f02563efe0a (patch)
tree9acef35b521f66672523bd1e0625d38abb102f67 /scripts/generate_rust_analyzer.py
parent52cae7f28ed6c3992489f16bb355f5b623f0912e (diff)
downloadlinux-e90db5521de2e00b63ba425b3b215f02563efe0a.tar.gz
linux-e90db5521de2e00b63ba425b3b215f02563efe0a.tar.bz2
linux-e90db5521de2e00b63ba425b3b215f02563efe0a.zip
kbuild: rust_is_available: check that environment variables are set
Sometimes [1] users may attempt to setup the Rust support by checking what Kbuild does and they end up finding out about `scripts/rust_is_available.sh`. Inevitably, they run the script directly, but unless they setup the required variables, the result of the script is not meaningful. We could add some defaults to the variables, but that could be confusing for those that may override the defaults (compared to their kernel builds), and `$CC` would not be a simple default in any case. Therefore, instead, explicitly check whether the expected variables are set (`$RUSTC`, `$BINDGEN` and `$CC`). If not, print an explanation about the fact that the script is meant to be called from Kbuild, since that is the most likely cause for the variables not being set. Link: https://lore.kernel.org/oe-kbuild-all/Y6r4mXz5NS0+HVXo@zn.tnic/ [1] Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com> Reviewed-by: Nathan Chancellor <nathan@kernel.org> Link: https://lore.kernel.org/r/20230616001631.463536-7-ojeda@kernel.org Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions