From 392b0a26f5fd8d3aedce7e0c15f9762a79312f01 Mon Sep 17 00:00:00 2001 From: Arnout Vandecappelle Date: Mon, 10 Jul 2017 01:21:23 +0200 Subject: [PATCH] toolchain-external: default BR2_TOOLCHAIN_EXTERNAL_PATH to empty It makes no sense to default to an arbitrary path. In addition, it in fact works correctly when it is empty. In that case, the toolchain will be searched in PATH. Update the help text to explain the above, and also that the compiler is supposed to be in the bin subdirectory. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni --- toolchain/toolchain-external/Config.in | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in index 4cd9ee4752..c4063b177b 100644 --- a/toolchain/toolchain-external/Config.in +++ b/toolchain/toolchain-external/Config.in @@ -67,10 +67,14 @@ endchoice config BR2_TOOLCHAIN_EXTERNAL_PATH string "Toolchain path" - default "/path/to/toolchain/usr" + default "" depends on BR2_TOOLCHAIN_EXTERNAL_PREINSTALLED help - Path to where the external toolchain is installed. + Path to where the external toolchain is installed. The + compiler itself is expected to be in the "bin" subdirectory + of this path. + + If empty, the compiler will be searched in $PATH. config BR2_TOOLCHAIN_EXTERNAL_GLIBC bool -- 2.30.2