From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Re: Re: [BROKEN] Windows host: -redir flag, console output, -nographic
Date: Tue, 12 Oct 2004 00:04:34 +0200 [thread overview]
Message-ID: <pan.2004.10.11.22.04.32.433121@reply.to> (raw)
In-Reply-To: 2ad73a041011120617db6ca7@mail.gmail.com
Le Mon, 11 Oct 2004 16:06:06 -0300, André Braga a écrit :
> On Mon, 11 Oct 2004 20:51:07 +0200, Ronald <look@reply.to> wrote:
>> For stdout I think the only way is to redirect output to a file, I know
>> this work for text output like help(perhaps it depends on SDL
>> redirection support). Windows has a something particular, a gui
>> application don't have a console with stdio attached by default, I
>> remember there was a patch to implement console support, kazu's qemu for
>> windows used it.
>
> Hmm, that's what I meant by "SDL linking flag"...
>
> Maybe this is blocking -nographic?
>
> So I guess everything is there, except that I'll have to enable them
> manually. Time to ressurrect my building environment on Windows... *sigh*
>
> Still, I don't think this is correct behavior. Not opening the initial
> console causes QEMU on Windows not to: 1) display console output in case
> of option misuse, or -h 2) support -nographic
>
> which is evil.
>
I don't know if qemu will works like this, but just to see I've
build qemu.exe without the -mwindows flag (like indicated in the patch),
qemu -h print the help on the dos prompt.
>
> cheers,
> A.
prev parent reply other threads:[~2004-10-11 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 17:52 [Qemu-devel] [BROKEN] Windows host: -redir flag, console output, -nographic André Braga
2004-10-11 18:10 ` [Qemu-devel] " Ronald
2004-10-11 18:34 ` André Braga
2004-10-11 18:51 ` [Qemu-devel] " Ronald
2004-10-11 19:06 ` André Braga
2004-10-11 22:04 ` Ronald [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=pan.2004.10.11.22.04.32.433121@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.