From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ui: add x_keymap.o to modules
Date: Thu, 17 May 2018 15:50:44 +0200 [thread overview]
Message-ID: <e54a1bf7-b154-844e-875c-87690754b7c0@redhat.com> (raw)
In-Reply-To: <20180517134559.uwne63xmqh2lucwq@sirius.home.kraxel.org>
On 17/05/2018 15:45, Gerd Hoffmann wrote:
> Hi,
>
>>> Related: can modules depend on modules, so we could make x_keymap a
>>> module of its own and have both gtk and sdl depend on it?
>>>
>>> That would also be useful when trying to modularize spice.
>>
>> How hard would it be to modularize the libspice-server side? The part
>> of the library that is used by QXL rendering should have much fewer
>> dependencies than the part that is used for keyboard, mouse, audio,
>> vmchannel/agent, etc.
>
> kbd, mouse, audio is needed on the client side and is not part of
> libspice-server anyway.
Yes, I'm talking about separating the client side from the QXL rendering
part.
> So spice is much less of a burden compared
> to sdl/gtk which bring alot of ui toolkit deps.
But SPICE does bring in 16 libraries, including both of NSS and OpenSSL...
Paolo
next prev parent reply other threads:[~2018-05-17 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 12:39 [Qemu-devel] [PATCH] ui: add x_keymap.o to modules Paolo Bonzini
2018-05-17 12:44 ` Daniel P. Berrangé
2018-05-17 12:50 ` Paolo Bonzini
2018-05-17 12:58 ` Daniel P. Berrangé
2018-05-17 12:51 ` Gerd Hoffmann
2018-05-17 12:54 ` Daniel P. Berrangé
2018-05-17 13:26 ` Paolo Bonzini
2018-05-17 13:45 ` Gerd Hoffmann
2018-05-17 13:50 ` Paolo Bonzini [this message]
2018-05-18 7:03 ` 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=e54a1bf7-b154-844e-875c-87690754b7c0@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@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).