qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Filip Navara <filip.navara@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	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 21:33:14 +0200	[thread overview]
Message-ID: <5b31733c0907091233s253dbb68l8e56e9d4900c49ef@mail.gmail.com> (raw)
In-Reply-To: <200907091808.06764.paul@codesourcery.com>

On Thu, Jul 9, 2009 at 7:08 PM, Paul Brook<paul@codesourcery.com> wrote:
>> > I think the chances of the user having appropriate toolchains readily
>> > available (without significant additional per-rom configury) are
>> > extremely slim.
>>
>> Actually, for x86, all of our ROMs will just use GCC so when building
>> x86 on x86, it's very likely the right tool chain is available.
>
> Except when it isn't, for example when building with a windows binary.
> 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.
>
> Paul

Actually windows binaries of MinGW can built this just fine, you just
have to link it to the native platform format (PE-COFF) and then
objcopy it to binary. The rest should work just like on Linux. I'm
building the BIOS from time to time on MinGW and while it is annoying
to modify the build files to work for MinGW I'd be happy to maintain
it for QEMU.

Best regards,
Filip Navara

      parent reply	other threads:[~2009-07-09 19:33 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
2009-07-09 19:33         ` Filip Navara [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=5b31733c0907091233s253dbb68l8e56e9d4900c49ef@mail.gmail.com \
    --to=filip.navara@gmail.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --cc=paul@codesourcery.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).