qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v3
Date: Wed, 18 Mar 2009 10:15:23 +0000	[thread overview]
Message-ID: <200903181015.24614.paul@codesourcery.com> (raw)
In-Reply-To: <49C099E4.9080503@redhat.com>

On Wednesday 18 March 2009, Avi Kivity wrote:
> Paul Brook wrote:
> >> This version uses a C tool to parse the options file instead of Perl
> >> script. I also added HXCOMM for comment purposes.
> >>
> >> Does this work on Windows?
> >
> > I'm pretty sure it doesn't work in cross environments.
>
> Just have qemu-user run the thing.

That's not going to work for several reasons:
- You might not be building qemu-user.
- qemu-user only supports a very small subset of systems. e.g. it's no use for 
linux->windows cross builds, which I expect to be the most common case
- The necessary runtime libraries might not be installed. Even if they are, 
qemu probably doesn't know where to find them.

Paul

  reply	other threads:[~2009-03-18 10:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 17:23 [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v3 Blue Swirl
2009-03-17 23:08 ` Paul Brook
2009-03-18  6:51   ` Avi Kivity
2009-03-18 10:15     ` Paul Brook [this message]
2009-03-18 10:18       ` Avi Kivity
2009-03-19 23:50       ` [Qemu-devel] Random thought about qemu-user and Windows Jamie Lokier
2009-03-19 23:56         ` Johannes Schindelin
2009-03-20 20:18         ` Stuart Brady
2009-03-21  9:13           ` Andreas Färber

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=200903181015.24614.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.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).