From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Jan Kiszka <jan.kiszka@web.de>, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Re: [PATCH] Drop roms from standard build
Date: Thu, 9 Jul 2009 17:19:43 +0100 [thread overview]
Message-ID: <200907091719.44828.paul@codesourcery.com> (raw)
In-Reply-To: <4A560FE7.4030906@us.ibm.com>
On Thursday 09 July 2009, Anthony Liguori wrote:
> Jan Kiszka wrote:
> > There is no point in generating and copying the optionsrom each time
> > qemu is build. It's a maintenance task given that we carry them as
> > binaries already. And that task could also be triggered explicitly via
> > 'make roms'. Solves the mingw32 build breakage, too.
>
> Yeah, it needs fixing but we absolutely want to build the roms as part
> of the normal build process.
I disagree. For the most part I'd expect roms to be better maintained as a
side project.
> When a user types make install from a source tarball, if they have the
> proper tool chain, we should be building everything from scratch and
> installing the versions that we built.
I think the chances of the user having appropriate toolchains readily
available (without significant additional per-rom configury) are extremely
slim.
Paul
next prev parent reply other threads:[~2009-07-09 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 7:12 [Qemu-devel] [PATCH] Drop roms from standard build Jan Kiszka
2009-07-09 7:52 ` [Qemu-devel] " Alexander Graf
2009-07-09 11:19 ` Jan Kiszka
2009-07-09 15:42 ` Anthony Liguori
2009-07-09 16:19 ` Paul Brook [this message]
2009-07-09 16:59 ` Anthony Liguori
2009-07-09 17:08 ` Paul Brook
2009-07-09 17:11 ` Anthony Liguori
2009-07-09 17:34 ` Paul Brook
2009-07-09 19:33 ` Filip Navara
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=200907091719.44828.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
/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 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.