From: Fam Zheng <famz@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] building user interfaces as modules
Date: Thu, 16 Nov 2017 08:08:53 +0800 [thread overview]
Message-ID: <20171116000853.GA14771@lemon> (raw)
In-Reply-To: <20171115121932.x4oh4aok5j5x6kxr@sirius.home.kraxel.org>
On Wed, 11/15 13:19, Gerd Hoffmann wrote:
> Hi,
>
> I'm trying to revamp the display initialization code:
>
> * First use a qapi type for the display options, so we can use
> -blockdev style command line parsing for -display (not there yet,
> but closer).
> * Second initialize all user interfaces the same way and build a
> registry for UIs. Drops lots of #ifdefs from vl.c
> * Finally this should make it *alot* easier to build user interfaces
> as modules.
>
> For SDL we already have sdl.mo defined in ui/Makefile.objs. so I tried
> that first. Just flipping CONFIG_SDL from 'y' to 'm' doesn't work
> though. sdl support isn't build, neither with nor without
> --enable-modules.
Perhaps you're missing a
common-obj-m += ui/
line in Makefile?
Fam
next prev parent reply other threads:[~2017-11-16 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 12:19 [Qemu-devel] building user interfaces as modules Gerd Hoffmann
2017-11-16 0:08 ` Fam Zheng [this message]
2017-11-16 7:07 ` 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=20171116000853.GA14771@lemon \
--to=famz@redhat.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 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).