[Buildroot] [PATCH v8 08/10] external-toolchain: check if a buildroot SDK has already been relocated

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Hello,

On Thu, 20 Jul 2017 16:35:19 +0200, Wolfgang Grandegger wrote:
> The location of the buildroot SDK is stored in the file "sdk-location"
> in "share/buildroot". If it's content does not match the current
> SDK location, ask the user to run the script "relocate-sdk.sh" in the
> top directory once. The external toolchain may be a pre-installed one
> in a directory that is not writeable by us. Therefore, we can't run
> the script directly.
> 
> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
> ---
>  toolchain/helpers.mk                                   | 16 ++++++++++++++++
>  toolchain/toolchain-external/pkg-toolchain-external.mk |  1 +
>  2 files changed, 17 insertions(+)

Now that I think of it, this is going to be a bit annoying. This means
that whenever you want to use a Buildroot-generated toolchain as an
external toolchain in another Buildroot configuration, you have to run
this relocate script.

This will break a lot of things, like the autobuilders, the runtime
test infrastructure, etc. that all rely on pre-built Buildroot
toolchains, but don't run the relocate-sdk script. In addition, we
simply can't do it, because it's directly Buildroot itself that
downloads the toolchain tarball and extracts it, so we don't even get
the opportunity to run the relocate-sdk script.

Therefore, I cannot apply this as-is, a better solution needs to be
found.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com