Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] BE: Buildroot How-To for QEMU/ARM (Jim Thomas)
Date: Sun, 31 Jan 2010 15:36:01 -0600	[thread overview]
Message-ID: <201001311536.04491.minimod@morethan.org> (raw)
In-Reply-To: <hk4kaq$l50$1@ger.gmane.org>

On Sun January 31 2010, Grant Edwards wrote:
> On 2010-01-31, Jim Thomas <jimthomasembedded@yahoo.com> wrote:
> 
> > I think the Buildroot adoption rate might be higher if there
> > were a documented, streamlined way to build the kernel/RFS and
> > execute it under QEMU, with an end-to-end Buildroot build
> > process triggered by a single 'some_arm_defconfig'.  It might
> > serve as a very useful hardware independent reference
> > platform.
> 
> I think that would be usefull as well.  Building for ARM boards
> and then running on Qemu is how I got up to speed on the
> Buildroot "environment", but it was harder than it could have
> been because the tutorials for buildroot/ARM/Qemu were out of
> date and the default configs for the two platforms I tried were
> broken (wouldn't build).
> 
> Keeping a tutorial up-to-date would take some effort. It might
> be easier if it were in a Wiki format that didn't require
> wrestling with the bug-tracker and the submissions and approval
> of patches.
> 
> If the default configs aren't going to be kept up to date, it
> would be nice if there was something to indicate which
> version(s) of Buildroot they did work with.
> 

depends on Broken
At the appropriate places would do that trick.

But don't ask for that - you'll probably get one of those:
"That requires the purchase of a commercial support contract."
answers since it involves the function of what is actually
produced by the build system, not the build system itself.

Mike
> It would be easy enough to set up an automated test to check
> that all of the default configs build, but checking to see if
> they work is obviously a lot harder.
> 

      reply	other threads:[~2010-01-31 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7759.1264608677.5110.buildroot@busybox.net>
2010-01-28  9:46 ` [Buildroot] BE: Buildroot How-To for QEMU/ARM (Jim Thomas) Vellemans, Noel
2010-01-30 17:01   ` Jim Thomas
2010-01-31 17:39     ` Jim Thomas
2010-01-31 19:06       ` Grant Edwards
2010-01-31 21:36         ` Michael S. Zick [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=201001311536.04491.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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