* [Buildroot] per-project uclibc configuration does not really work
@ 2007-11-01 7:07 Hamish Moffatt
2007-11-01 11:17 ` Bernhard Fischer
0 siblings, 1 reply; 2+ messages in thread
From: Hamish Moffatt @ 2007-11-01 7:07 UTC (permalink / raw
To: buildroot
buildroot's project support (eg saveconfig target) appears to offer
per-project uClibc .config support and per-project uClibc version
selection.
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).
Is there much benefit in trying to share package builds between
projects, as buildroot does right now?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] per-project uclibc configuration does not really work
2007-11-01 7:07 [Buildroot] per-project uclibc configuration does not really work Hamish Moffatt
@ 2007-11-01 11:17 ` Bernhard Fischer
0 siblings, 0 replies; 2+ messages in thread
From: Bernhard Fischer @ 2007-11-01 11:17 UTC (permalink / raw
To: buildroot
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
>selection.
>
>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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-01 11:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-01 7:07 [Buildroot] per-project uclibc configuration does not really work Hamish Moffatt
2007-11-01 11:17 ` Bernhard Fischer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.