Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's the buildroot attitude to u-boot building?
Date: Sat, 22 Feb 2014 00:04:28 +0100	[thread overview]
Message-ID: <20140222000428.77575be9@skate> (raw)
In-Reply-To: <le7p26$n75$1@ger.gmane.org>

Dear Grant Edwards,

On Fri, 21 Feb 2014 14:49:43 +0000 (UTC), Grant Edwards wrote:

> I messed with using buildroot for building U-Boot, and decided it was
> better to build it outside of buildroot.  I found buildroot great for
> building a root filesystem, but I didn't find it useful for other
> things (like building toolchains, bootloaders, kernels, etc.).  I
> think it makes a lot more sense to build those separately.

Do you have more details about what you found unpractical in Buildroot
to build U-Boot and your kernel? What issues did you had, or things you
found not really nice?

Thanks for your feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-02-21 23:04 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 [this message]
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
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=20140222000428.77575be9@skate \
    --to=thomas.petazzoni@free-electrons.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