[Buildroot] [PATCH] Allow Buildroot to update toolchain
ANDY KENNEDY
ANDY.KENNEDY at adtran.com
Fri Sep 27 14:56:33 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.
Oh, really? I totally missed that then. I remember when that came
out (like last year sometime, right?) but I didn't really look into
it that much.
Well, cool! I guess I reinvented the wheel on this one, eh?
I guess I'll try your way then and see what happens ;).
If it works exactly as what I'm doing that's cool!
>
> Or maybe I misunderstanding the use case?
Um, yeah, that's it. It isn't that I'm goofy or anything ;).
Andy
More information about the buildroot
mailing list