From: Paul Brook <paul@codesourcery.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Re: [PATCH] Drop roms from standard build
Date: Thu, 9 Jul 2009 18:34:20 +0100 [thread overview]
Message-ID: <200907091834.22163.paul@codesourcery.com> (raw)
In-Reply-To: <4A5624D6.8060007@us.ibm.com>
> > Also, x86 is only one of many targets qemu supports. If you're serious
> > about rebuilding roms as standard, then at bare minimum you need to
> > handle sparc and ppc as well as x86.
>
> Yup. That's why we need to probe for toolchains in order to determine
> whether roms can be built. If you're a developer making changes to
> OpenBIOS, clearly you are going to have the appropriate tool chains
> installed.
IMO a developer changes to a rom is a special case.
If you're arguing that roms should be built by default, for everyone, then I
disagree and don't think this is feasible. Most users simply don't have the
prerequisites, and don't want to have to cofigure everything even when they
do. If you care about this (for reproducibility or licencing reasons) then it
should be all or nothing. I don't buy "It works for x86-on-x86 most of the
time" as a valid argument for anything. We either build things by default, or
we include binaries, not both.
If you're talking about developers modifying the roms, then most of the
arguments above still apply. Chances are you're only actually interested in
one rom anyway, so building it separately really isn't significant extra
hassle.
Having everything in one source tree maybe makes sense. Except that most roms
are already used by several projects. What you really want is to coordinate
releases with the upstream maintainers, having a qemu branck/fork if it's
really that hard to get changes integrated back. In the case of the pc-bios
it probably wants to be split into a sparate project, rather than being part
of bochs.
Paul
next prev parent reply other threads:[~2009-07-09 17:34 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
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 [this message]
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=200907091834.22163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).