toolchain-external: default BR2_TOOLCHAIN_EXTERNAL_PATH to empty
authorArnout Vandecappelle <arnout@mind.be>
Sun, 9 Jul 2017 23:21:23 +0000 (01:21 +0200)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Mon, 10 Jul 2017 16:03:13 +0000 (18:03 +0200)
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) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
toolchain/toolchain-external/Config.in

index 4cd9ee4752cd3bafc0f5f381a1242c9b7c7ba840..c4063b177b942d52b3413603522b25d9686e8902 100644 (file)
@@ -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