From: Riku Voipio <riku.voipio@iki.fi>
To: Jamie Lokier <jamie@shareable.org>
Cc: Alex Graf <alex@csgraf.de>, Anthony Liguori <aliguori@us.ibm.com>,
Avi Kivity <avi@redhat.com>,
qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>
Subject: Re: [Qemu-devel] Re: [PATCH 3/4] Update makefile to build roms
Date: Mon, 18 May 2009 11:25:03 +0300 [thread overview]
Message-ID: <20090518082503.GA12681@kos.to> (raw)
In-Reply-To: <20090518042445.GD32609@shareable.org>
On Mon, May 18, 2009 at 05:24:45AM +0100, Jamie Lokier wrote:
> Paul Brook wrote:
> > > Having multiple packages therefore makes little sense because they can
> > > never be independent of each other.
> > Depends how your build system is setup. IMHO building a ROM and
> > building qemu itself are different tasks that effectively need
> > separate packages anyway.
> And when built for a distribution, perhaps QEMU, BIOS and PXE should
> be separate packages anyway, with QEMU depending on the others (or
> perhaps "recommending").
This is indeed how it is done in Debian, roms are built in separate packages.
There is also the complication of building ROMs for non-native archs.
Say building openbios-sparc when building qemu on x86, or vgabios when
building qemu on ppc. Then you need a crosscompiler at hand.
While it is not useful for distributions, making it possible to build roms as
part of qemu build process is still usefull for people hacking on qemu.
next prev parent reply other threads:[~2009-05-18 8:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 15:28 [Qemu-devel] [PATCH 0/4][RFC] Bring ROM source into tree via git submodules Anthony Liguori
2009-05-17 15:28 ` [Qemu-devel] [PATCH 1/4] Add GPL bios as a submodule Anthony Liguori
2009-05-17 15:43 ` [Qemu-devel] " Avi Kivity
2009-05-17 15:49 ` Anthony Liguori
2009-05-17 16:23 ` Avi Kivity
2009-05-17 17:51 ` Jamie Lokier
2009-05-17 18:03 ` Avi Kivity
2009-05-17 18:05 ` Stanislav
2009-05-17 18:11 ` Avi Kivity
2009-05-17 18:37 ` Stanislav
2009-05-17 19:07 ` Avi Kivity
2009-05-17 22:12 ` Carl-Daniel Hailfinger
2009-05-17 22:40 ` Avi Kivity
2009-05-17 23:22 ` Anthony Liguori
2009-05-18 15:20 ` ron minnich
2009-05-18 2:40 ` Kevin O'Connor
2009-05-17 23:13 ` Anthony Liguori
2009-05-18 4:22 ` Jamie Lokier
2009-05-25 13:04 ` Carl-Daniel Hailfinger
2009-05-17 23:09 ` Anthony Liguori
2009-05-17 23:23 ` Avi Kivity
2009-05-17 23:31 ` Anthony Liguori
2009-05-17 23:40 ` Avi Kivity
2009-05-18 1:17 ` Anthony Liguori
2009-05-18 5:48 ` Avi Kivity
2009-05-17 17:10 ` Sebastian Herbszt
2009-05-17 15:28 ` [Qemu-devel] [PATCH 2/4] Add submodule for VGABios Anthony Liguori
2009-05-17 15:29 ` [Qemu-devel] [PATCH 3/4] Update makefile to build roms Anthony Liguori
2009-05-17 15:46 ` [Qemu-devel] " Avi Kivity
2009-05-17 15:47 ` Avi Kivity
2009-05-17 15:53 ` Anthony Liguori
2009-05-17 17:16 ` Avi Kivity
2009-05-17 23:10 ` Anthony Liguori
2009-05-17 22:04 ` Paul Brook
2009-05-17 23:28 ` Anthony Liguori
2009-05-17 23:43 ` Paul Brook
2009-05-18 1:18 ` Anthony Liguori
2009-05-18 4:24 ` Jamie Lokier
2009-05-18 8:25 ` Riku Voipio [this message]
2009-05-18 8:35 ` Avi Kivity
2009-05-17 15:29 ` [Qemu-devel] [PATCH 4/4] Allow tool chain to be specified for bios build Anthony Liguori
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=20090518082503.GA12681@kos.to \
--to=riku.voipio@iki.fi \
--cc=alex@csgraf.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=jamie@shareable.org \
--cc=kirkland@canonical.com \
--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).