From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] per-project uclibc configuration does not really work
Date: Thu, 1 Nov 2007 12:17:28 +0100 [thread overview]
Message-ID: <20071101111726.GI1869@aon.at> (raw)
In-Reply-To: <20071101070728.GA21168@cloud.net.au>
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.
prev parent reply other threads:[~2007-11-01 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 7:07 [Buildroot] per-project uclibc configuration does not really work Hamish Moffatt
2007-11-01 11:17 ` Bernhard Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071101111726.GI1869@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox