From: Stefan Weil <sw@weilnetz.de>
To: qemu-devel@nongnu.org
Cc: Stefan Weil <sw@weilnetz.de>
Subject: [Qemu-devel] [PATCH] w32: QEMU applications with SDL are always GUI applications
Date: Sat, 3 Dec 2011 22:32:21 +0100 [thread overview]
Message-ID: <1322947941-8521-1-git-send-email-sw@weilnetz.de> (raw)
Since commit 1d14ffa97eacd3cb722271eaf6f093038396eac4 (in 2005),
QEMU applications on W32 don't use the default SDL compiler flags:
Instead of a GUI application, a console application is created.
This has disadvantages (there is always an empty console window) and
no obvious reason, so this patch removes the strange flag modification.
The SDL GUI applications still can be run from a console window
and even send stdout and stderr to that console by setting environment
variable SDL_STDIO_REDIRECT=no.
Signed-off-by: Stefan Weil <sw@weilnetz.de>
---
configure | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
index ac4840d..f2fdb1d 100755
--- a/configure
+++ b/configure
@@ -1522,9 +1522,6 @@ EOF
if compile_prog "$sdl_cflags" "$sdl_libs" ; then
sdl_libs="$sdl_libs -lX11"
fi
- if test "$mingw32" = "yes" ; then
- sdl_libs="`echo $sdl_libs | sed s/-mwindows//g` -mconsole"
- fi
libs_softmmu="$sdl_libs $libs_softmmu"
fi
--
1.7.2.5
next reply other threads:[~2011-12-03 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 21:32 Stefan Weil [this message]
2011-12-11 16:50 ` [Qemu-devel] [PATCH] w32: QEMU applications with SDL are always GUI applications 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
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=1322947941-8521-1-git-send-email-sw@weilnetz.de \
--to=sw@weilnetz.de \
--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).