From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Status of SDL2 and GTK displays: can we make display modular?
Date: Mon, 22 Jun 2015 15:00:42 +0300 [thread overview]
Message-ID: <5587F8EA.8030403@msgid.tls.msk.ru> (raw)
Hello.
What's the current status of SDL2 and GTK support?
Last time I checked and asked, there were some missing
pieces in SDL2 compared with SDL1, basically making
SDL2 unusable (again, compared with SDL1).
GTK backend, besides the menu, does not add any noticeable
functionality to SDL1 interface, but adds a lot of extra
dependencies. This, and also the fact that at least
initial GTK support was incomplete, was the reasons why
in Debian we didn't change default display backend from
SDL1 to GTK when qemu changed the default.
Now I wonder if we can finally switch to SDL2 and/or to
GTK, and maybe even make the display backend dynamically
loadable in the same way as block device backends are
these days.
With loadable display backend it will be the last bastion
for many people who are asking for "minimal QEMU for
servers" which is supposed to not have any X deps.
I started working on loadable display backend a few
years ago, but quickly discovered that SDL1 can't be
loaded dynamically, at least on some platforms where
it substitutes main() function in order to do some
initialization (as if there's no support for constructors).
So now I'm asking again whenever current GTK and SDL2
supports are complete enough to replace SDL1.
Thanks,
/mjt
next reply other threads:[~2015-06-22 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 12:00 Michael Tokarev [this message]
2015-06-22 12:34 ` [Qemu-devel] Status of SDL2 and GTK displays: can we make display modular? Paolo Bonzini
2015-06-22 15:24 ` Gerd Hoffmann
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=5587F8EA.8030403@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--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.