[Buildroot] [PATCH] Allow Buildroot to update toolchain

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

Dear ANDY KENNEDY,

On Thu, 26 Sep 2013 20:34:40 +0000, ANDY KENNEDY wrote:

> Oh, my bad.  I mean for when one uses an external toolchain.  For
> example:
> 
> I build a toolchain using Crosstool-NG.  I have a few libraries in
> there, but to fully use this as a cross compiler I need things like
> ncurses, pcap, lttng, etc.  In this case, I would either need to have
> some sort of SYSROOT configured. It is not always desirable to have
> those two items disjoined.  So, I dump my additional libraries into
> the toolchain.

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.

Or maybe I misunderstanding the use case?

Best regards,

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