[Buildroot] [PATCH v8 08/10] external-toolchain: check if a buildroot SDK has already been relocated
Arnout Vandecappelle
arnout at mind.be
Sat Jul 22 10:49:18 UTC 2017
On 21-07-17 22:40, Thomas Petazzoni wrote:
> 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.
No it doesn't. Buildroot doesn't use the external toolchain as-is; the relevant
files are copied to STAGING_DIR. Only the gcc related includes are still used
from HOST_DIR/opt/ext-toolchain. Just do a gcc -v link and you'll see.
[snip]
>> 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 :/
Since Buildroot doesn't use anything from HOSTDIR/opt/ext-toolchain,
"relocating" it isn't relevant.
Bottom line: indeed this patch should be dropped.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
More information about the buildroot
mailing list