[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 Fri, 21 Jul 2017 22:31:48 +0200, Arnout Vandecappelle wrote:

>  This is not true. I already regularly use a Buildroot SDK in projects by
> setting BR2_HOST_DIR=/opt/... and packaging that. This SDK is then used to
> create a rootfs+kernel with Buildroot, and separately to build applications.
> Since the applications need some additional libraries, these libraries are
> included in the SDK. They are not used by Buildroot, so it's double work (they
> are included in the SDK, and built again for the target rootfs).

This is really horrible, because it means that some libraries that
Buildroot doesn't know about may be present in the toolchain sysroot,
be detected by packages, etc.

>  Admittedly it's not perfect, but it works. At least, as long as you don't go
> and update Buildroot (thus putting new versions of the libraries on the target)
> without updating the SDK as well.
> 
>  However...
> 
> >>> And therefore, the
> >>> relocate-sdk procedure is useless, because there's nothing to relocate
> >>> in an SDK that is just a toolchain.    
> >>
> >> OK. I see. Then I will drop this patch.  
> > 
> > Let's see if Arnout agrees with my reasoning. Quite often he points me
> > at details I have missed :-)  
> 
>  relocate-sdk is still useless when using it as an external toolchain. You could
> say it makes sense for a pre-installed toolchain, but then only if you're using
> that SDK outside of Buildroot. Buildroot is not going to use any of the
> additional stuff.

Sorry, but I did not understand this paragraph :/

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