[Buildroot] [PATCHv2] toolchain-external: add a specific check to avoid Angstrom toolchains
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Tue Oct 22 14:30:25 UTC 2013
Peter, Arnout,
On Tue, 22 Oct 2013 16:24:24 +0200, Peter Korsgaard wrote:
> > Just for my info, how is it possible that we cannot use such an
> > Angstrom toolchain as an external toolchain, but it is possible to use
> > a buildroot-generated one? We can also generate a host dir with loads
> > of libs, and these are perfectly usable as external toolchain, right?
>
> No, we can afaik only reuse a buildroot toolchain if it is "bare",
> E.G. no packages selected.
Yes, absolutely. Ideally, my check for "angstrom" toolchain shouldn't
check for angstrom, but should instead validate that the toolchain is
"pure" (i.e only the C library). Unfortunately, I don't quite see an
easy and reliable way to make sure that the only libraries/headers
provided are the ones of the C library.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
More information about the buildroot
mailing list