All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/5] gtk: add opengl support, using egl
Date: Sat, 23 May 2015 19:44:04 +0200	[thread overview]
Message-ID: <5560BC64.6060600@redhat.com> (raw)
In-Reply-To: <1432135182-29676-5-git-send-email-kraxel@redhat.com>

On 20.05.2015 17:19, Gerd Hoffmann wrote:
> This adds opengl rendering support to the gtk ui, using egl.
> It's off by default for now, use 'qemu -display gtk,gl=on'
> to play with this.
>
> Note that gtk got native opengl support with release 3.16.
> There most likely will be a separate implementation for 3.16+,
> using the native gtk opengl support.  This patch covers older
> versions (and for the time being 3.16 too, hopefully without
> rendering quirks).
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>   include/ui/console.h |   2 +-
>   include/ui/gtk.h     |  23 +++++++++
>   ui/Makefile.objs     |   3 ++
>   ui/gtk-egl.c         | 141 +++++++++++++++++++++++++++++++++++++++++++++++++++
>   ui/gtk.c             |  77 ++++++++++++++++++++++------
>   vl.c                 |  11 +++-
>   6 files changed, 240 insertions(+), 17 deletions(-)
>   create mode 100644 ui/gtk-egl.c

I do see the quandary with gtk 3.14 and 3.15 
(gtk_widget_set_double_buffered() is deprecated, but we need it), but 
the problem is, with this patch, you simply cannot compile qemu on a gtk 
3.14+ system with --with-gtkabi=3.0 and without --disable-opengl, which 
I don't think is right.

So at least the commit message is wrong, this patch does not cover 3.16. 
It would without -Werror (or with -Wno-deprecated-declarations), but 
that's enabled by default.

Once the native OpenGL support introduced by 3.16 is used, at least 
that'll be covered, but we'll still have to deal with 3.14 and 3.15. I 
think the right thing to do is to make configure disable OpenGL support 
if gtk 3.14+ is to be used (in the future, that would be 3.14/3.15 
only). That, or pass -Wno-deprecated-declarations for compiling 
ui/gtk.c, but that seems very ugly to me.

Not planning to have OpenGL support for 3.14/3.15 I think is fine, but 
we have to make sure that OpenGL support cannot be silently enabled by 
configure and then break compilation of qemu.

Max

  reply	other threads:[~2015-05-23 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 15:19 [Qemu-devel] [PATCH v2 0/5] gtk: add opengl support Gerd Hoffmann
2015-05-20 15:19 ` [Qemu-devel] [PATCH v2 1/5] ui: use libexpoxy Gerd Hoffmann
2015-05-20 15:19 ` [Qemu-devel] [PATCH v2 2/5] ui: shader.h protect against double inclusion Gerd Hoffmann
2015-05-20 15:19 ` [Qemu-devel] [PATCH v2 3/5] ui: add egl-helpers Gerd Hoffmann
2015-05-23 17:36   ` Max Reitz
2015-05-20 15:19 ` [Qemu-devel] [PATCH v2 4/5] gtk: add opengl support, using egl Gerd Hoffmann
2015-05-23 17:44   ` Max Reitz [this message]
2015-05-26  6:35     ` Gerd Hoffmann
2015-05-26 12:56       ` Gerd Hoffmann
2015-05-26 14:06         ` Max Reitz
2015-05-26 14:12           ` Gerd Hoffmann
2015-05-20 15:19 ` [Qemu-devel] [PATCH v2 5/5] gtk: Replace gdk_cursor_new() 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=5560BC64.6060600@redhat.com \
    --to=mreitz@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.