From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Configure check for graphical output
Date: Tue, 31 May 2005 19:35:34 +0100 [thread overview]
Message-ID: <200505311935.34621.paul@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
The qemu configure script will silently disable graphical output if it can't
find a suitable output library (ie. SDL). This is a very common source of
confusion for people building qemu for the first time. It's not obvious from
the configure output that SDL is effectively required for normal operation.
The attached patch changes the default behaviour so that configure will issue
an error if a user tries configure full system emulation without graphical
output. It also adds an option to suppress this check for users who know what
they are doing.
Paul
[-- Attachment #2: patch.qemu_gfx --]
[-- Type: text/x-diff, Size: 1081 bytes --]
Index: configure
===================================================================
RCS file: /cvsroot/qemu/qemu/configure,v
retrieving revision 1.66
diff -u -p -r1.66 configure
--- configure 28 Apr 2005 20:41:53 -0000 1.66
+++ configure 31 May 2005 17:59:51 -0000
@@ -84,6 +84,7 @@ linux="no"
kqemu="no"
kernel_path=""
cocoa="no"
+check_gfx="yes"
# OS specific
targetos=`uname -s`
@@ -186,6 +187,8 @@ for opt do
;;
--enable-cocoa) cocoa="yes" ; sdl="no"
;;
+ --disable-gfx-check) check_gfx="no"
+ ;;
esac
done
@@ -604,6 +607,14 @@ if expr $target : '.*-user' > /dev/null
target_user_only="yes"
fi
+if test "$target_user_only" = "no" -a "$check_gfx" = "yes" \
+ -a "$sdl" = "no" -a "$cocoa" = "no" ; then
+ echo "ERROR: QEMU requires SDL or Cocoa for graphical output"
+ echo "To build QEMU with graphical output configure with --disable-gfx-check"
+ echo "Note that this will disable all output from the virtual graphics card."
+ exit 1;
+fi
+
#echo "Creating $config_mak, $config_h and $target_dir/Makefile"
mkdir -p $target_dir
reply other threads:[~2005-05-31 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200505311935.34621.paul@codesourcery.com \
--to=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).