From: Stefan Weil <sw@weilnetz.de>
To: TeLeMan <geleman@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] w32: QEMU applications with SDL are always GUI applications
Date: Thu, 22 Dec 2011 07:45:44 +0100 [thread overview]
Message-ID: <4EF2D218.8080401@weilnetz.de> (raw)
In-Reply-To: <CAETRQW=4k6sELueQDF9W48wNN=wx1CS-JX7WZT+CSohXO_XDUw@mail.gmail.com>
Am 22.12.2011 02:50, schrieb TeLeMan:
> SDL-1.3 removed the stdio-redirect feature, so we should ignore it.
>
> Blue Swirl, can you revert this commit?
I'd prefer to keep it. There are good reason why SDL applications
are linked as Windows applications by default, so we should use
this default.
Yes, it's no perfect solution, but even for developers who want
to see stdout and stderr, it works when you use a rxvt console
or something equivalent.
You said that you use a self-compiled SDL library.
Then you can change your sdl-config or sdl.pc so that it
sets the SDL linker options according to your needs.
What about my proposal to create each system emulation in two
variants (qemu-system-i386.exe, qemu-system-i386w.exe)?
Do you think this might be a solution which fits everybody's
needs?
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-12-22 6:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 21:32 [Qemu-devel] [PATCH] w32: QEMU applications with SDL are always GUI applications Stefan Weil
2011-12-11 16:50 ` Blue Swirl
2011-12-16 3:24 ` TeLeMan
2011-12-16 23:12 ` Stefan Weil
2011-12-19 2:12 ` TeLeMan
2011-12-19 8:15 ` Stefan Weil
2011-12-19 9:31 ` TeLeMan
2011-12-19 10:17 ` Andreas Färber
2011-12-22 1:50 ` TeLeMan
2011-12-22 6:45 ` Stefan Weil [this message]
2011-12-22 7:26 ` TeLeMan
2011-12-22 8:03 ` [Qemu-devel] [PATCH] w32: Build windows and console executables Stefan Weil
2011-12-22 9:22 ` TeLeMan
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=4EF2D218.8080401@weilnetz.de \
--to=sw@weilnetz.de \
--cc=blauwirbel@gmail.com \
--cc=geleman@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 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.