From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's the buildroot attitude to u-boot building?
Date: Sun, 23 Feb 2014 18:50:53 +0000 (UTC) [thread overview]
Message-ID: <ledfud$cnf$1@ger.gmane.org> (raw)
In-Reply-To: 20140223111839.1ef569b9@skate
On 2014-02-23, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> I guess here it's really a matter of taste.
True.
> I've seen a large of number of people/companies who really like the
> fact that one *single* Buildroot configuration is building their
> entire embedded Linux system: toolchain, rootfs, kernel and
> bootloader images.
If those make up the entire embedded Linux system, then that would be
convenient.
> It is indeed clear that Buildroot used to be mainly aimed at
> "integration", not to be used during development work.
>
> However, based on what you say, it really looks like you have never
> looked at using <pkg>_OVERRIDE_SRCDIR together with "make
><pkg>-rebuild", because they do precisely what you're looking for :-)
Indeed, I wasn't aware of those. It looks like they were added after I
decided to build kernel and boot-loader independently.
next prev parent reply other threads:[~2014-02-23 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 1:53 [Buildroot] What's the buildroot attitude to u-boot building? Charles Manning
2014-02-21 14:49 ` Grant Edwards
2014-02-21 23:04 ` Thomas Petazzoni
2014-02-22 20:45 ` Grant Edwards
2014-02-23 0:05 ` Mike Zick
2014-02-23 10:18 ` Thomas Petazzoni
2014-02-23 18:50 ` Grant Edwards [this message]
2014-02-23 19:56 ` Mike Zick
2014-02-21 23:13 ` Thomas Petazzoni
2014-02-24 1:33 ` Charles Manning
2014-02-24 8:37 ` Peter Korsgaard
2014-03-18 5:21 ` Thomas Petazzoni
2014-03-18 8:05 ` Peter Korsgaard
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='ledfud$cnf$1@ger.gmane.org' \
--to=grant.b.edwards@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