From: Scott Wood <scottwood@freescale.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Thu, 13 Dec 2012 09:57:32 -0600 [thread overview]
Message-ID: <1355414252.14046.1@snotra> (raw)
In-Reply-To: <50C9F16A.2070602@redhat.com> (from kraxel@redhat.com on Thu Dec 13 09:16:58 2012)
On 12/13/2012 09:16:58 AM, Gerd Hoffmann wrote:
> Hi,
>
> >> A pretty central data structure in qemu (DisplayState /
> >> DisplaySurface) carries a pixman image, not some module which can
> >> easily be made optional. Just look at the tons of #ifdef'ery you
> >> have to do to get this going.
> >
> > His point is that anything related to DisplayState should be
> > optional.
>
> We can try, but sprinkling #ifdefs all over the place isn't the way to
> go. Separate any Display* stuff, say to display.[ch]. Include
> display.h only when needed. Then not compiling the object files
> will do the trick, and maybe one or two #ifdefs in vl.c.
>
> At least in theory. In practice it probably needs some more cleanups
> so
> it actually works.
That's fine. This patch was more of a quick hack to show that it's
possible, and to start a conversation about whether a cleaner approach
would be accepted if the effort were spent on it.
> And the "not compiling" part brings us back to the "easy way to strip
> down qemu" part. I'd love to have something (kconfig?) which allows
> to
> pick which device emulations, block formats, ... I wanna include into
> qemu.
Yes, kconfig would be very nice.
-Scott
next prev parent reply other threads:[~2012-12-13 15:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 3:18 [Qemu-devel] [RFC PATCH] Allow building without graphics support Scott Wood
2012-12-12 6:46 ` Stefan Weil
2012-12-13 0:48 ` Scott Wood
2012-12-13 6:31 ` Stefan Weil
2012-12-13 15:53 ` Scott Wood
2012-12-13 18:58 ` Stefan Weil
2012-12-13 19:16 ` Scott Wood
2012-12-13 19:32 ` Scott Wood
2012-12-14 8:13 ` Gerd Hoffmann
2012-12-14 18:51 ` Scott Wood
2012-12-19 9:02 ` Gerd Hoffmann
2012-12-19 18:47 ` Scott Wood
2012-12-14 8:07 ` Gerd Hoffmann
2012-12-14 18:48 ` Scott Wood
2012-12-19 9:13 ` Gerd Hoffmann
2012-12-19 18:57 ` Scott Wood
2012-12-20 6:59 ` Gerd Hoffmann
2012-12-20 16:19 ` Scott Wood
2012-12-21 8:56 ` Gerd Hoffmann
2012-12-21 10:56 ` Robert Schiele
2012-12-21 19:01 ` Scott Wood
2012-12-12 7:52 ` Gerd Hoffmann
2012-12-13 0:57 ` Scott Wood
2012-12-13 7:16 ` Gerd Hoffmann
2012-12-13 14:44 ` Alexander Graf
2012-12-13 15:10 ` Peter Maydell
2012-12-13 15:16 ` Gerd Hoffmann
2012-12-13 15:30 ` Alexander Graf
2012-12-13 15:57 ` Scott Wood [this message]
2012-12-12 16:28 ` John Spencer
2012-12-12 16:54 ` Andreas Färber
2012-12-13 0:53 ` Scott Wood
2012-12-12 16:47 ` Peter Maydell
2012-12-12 17:09 ` Andreas Färber
2012-12-12 17:37 ` Peter Maydell
2012-12-12 17:42 ` Paolo Bonzini
2012-12-13 0:51 ` Scott Wood
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=1355414252.14046.1@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.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.