From: Jan Kiszka <jan.kiszka@web.de>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] Drop roms from standard build
Date: Thu, 09 Jul 2009 13:19:31 +0200 [thread overview]
Message-ID: <4A55D243.4020802@web.de> (raw)
In-Reply-To: <1AF80EC2-8B2F-43CF-9C50-984B0F5243C2@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Alexander Graf wrote:
>
>
>
>
> On 09.07.2009, at 09:12, Jan Kiszka <jan.kiszka@web.de> 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.
>
> Well, Anthony specifically asked me to make the roms get built
> automatically whenever possible.
>
> So that behavior is actually on purpose :-)
Then quite a few things need to be fixed:
- host tool generation (signrom, I think there were several approached
under discussion - but what is preferred now?)
- disabling the build for incompatible tool chains (mingw32?)
- do not automatically copy stuff into the source dir (absolute no-go
if you want to keep it clean from build outputs)
So for now I would simply disable the build - unless I missed that there
are already patches pending to fix all this.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-07-09 11: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 [this message]
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
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=4A55D243.4020802@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.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).