From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] ui: add x_keymap.o to modules
Date: Thu, 17 May 2018 13:58:43 +0100 [thread overview]
Message-ID: <20180517125843.GL5657@redhat.com> (raw)
In-Reply-To: <feddfb98-318a-d5ca-1aee-76f99fc52ce8@redhat.com>
On Thu, May 17, 2018 at 02:50:04PM +0200, Paolo Bonzini wrote:
> On 17/05/2018 14:44, Daniel P. Berrangé wrote:
> >> +ifeq ($(CONFIG_X11),y)
> >> +sdl.mo-objs += x_keymap.o
> >> +gtk.mo-objs += x_keymap.o
> > Would this cause symbol clash if both sdl & gtk modules are loaded
> > at the same time, or have we used linker scripts to limit what symbols
> > each module exposes ?
> >
>
> We don't, but: 1) the file has only functions and no data; 2) in any
> case the symbols are the same, so it is not a real clash.
Ok, as long as dlopen() doesn't whine its fine with me.
> Adding linker scripts would be a nice improvement, but it is not
> necessary for this patch.
Agreed.
> Another possibility would be to include x_keymap.c in the files that use
> it and make qemu_xkeymap_mapping_table static, but I think it would be
> the worst.
It isn't worth trying to be too clever since we're deleting SDL1 in
the 2.14 dev cycle.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-05-17 12:58 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é [this message]
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
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=20180517125843.GL5657@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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.