[Buildroot] [PATCH] Allow Buildroot to update toolchain

ANDY KENNEDY ANDY.KENNEDY at adtran.com
Fri Sep 27 15:08:30 UTC 2013


> I still don't understand. What you're explaining is exactly what
> Buildroot is doing today. When you use an external toolchain, Buildroot
> copies the toolchain sysroot (which contains just the C library) in
> output/staging and then progressively "improves" this sysroot by adding
> all the libraries that have been cross-compiled for your target.
> 
> If what you need is then the ability to deliver this toolchain to
> application developers who will not be using Buildroot, but need a
> toolchain with all the libraries, then the proper way to do this is, as
> Peter suggested, to do BR2_HOST_DIR=/opt/some-location/, then do your
> Buildroot build, tarball /opt/some-location/ and deliver that as the
> toolchain to be used by your application developers.

Thomas/Peter/all:

The following blurb (from the help menu) doesn't really say what
you said above:

Directory to store all the binary files that are built for the host.
This includes the cross compilation toolchain when building the
internal buildroot toolchain.

What the above says to me is that aclocal, automake, bison, flex,
etc will end up in my toolchain.  I don't really want this.

Now, if using an external toolchain changes this statement to what
you said "then progressively "improves" this sysroot by adding
all the libraries that have been cross-compiled for your target."
without making a bunch of additional build tools in there (which
won't really be needed in the follow-on builds by developers not
using Buildroot), then we probably need to specify this.  Otherwise,
my patch ONLY updates the sysroot and does not dump a bunch of
library compile time junk into the toolchain (never to be used
again).

Andy


More information about the buildroot mailing list