[Buildroot] per-project uclibc configuration does not really work

Bernhard Fischer rep.dot.nop at gmail.com
Thu Nov 1 11:17:28 UTC 2007

On Thu, Nov 01, 2007 at 06:07:28PM +1100, Hamish Moffatt wrote:
>buildroot's project support (eg saveconfig target) appears to offer
>per-project uClibc .config support and per-project uClibc version
>However, uclibc is built into the per-arch toolchain_build_$(ARCH) 
>directory and installed into build_$(ARCH), rather than the per-project
>build directory project_build_$(ARCH)/$(PROJECT). And so is the gcc
>cross-compiler built against that uclibc.
>Only a few packages build into the per-project build directly, name
>busybox and uclibc. The problem is that if you change your uclibc
>configuration you may well need to rebuild all your programs too,
>because autoconf tests might return different results etc.
>Effectively you have to build everything per-project (including the
>whole toolchain).

See "using PROJECTs with buildroot" in the archives.
>Is there much benefit in trying to share package builds between
>projects, as buildroot does right now?

I don't think so.

More information about the buildroot mailing list