From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org,
schnitzeltony@googlemail.com, otavio.salvador@ossystems.com.br
Subject: [PATCH 0/1] Fix Gtk+3 initialization without GLX
Date: Wed, 21 Oct 2015 11:34:20 +0300 [thread overview]
Message-ID: <cover.1445415749.git.jussi.kukkonen@intel.com> (raw)
Following patch should fix the issue of Gtk+3 applications exiting
when started in systems without libGL.so.1. The issue needs to be
solved with upstreams (epoxy, possibly Gtk) in future releases but
for 2.0 this should do it.
This patch does not change the advice to application recipes: If
the application uses OpenGL in GLArea, it should RDEPEND on libgl.
Jussi
The following changes since commit 556c0ea92eb32ddb9c9a5e30a74b2ca24ac69c68:
lib/oe/image.py: Fix dependency handling for compressed types (2015-10-14 18:08:37 +0300)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jku/gtk-gl-again
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/gtk-gl-again
Jussi Kukkonen (1):
gtk+3: Do not try to initialize GL without libgl
meta/recipes-gnome/gtk+/gtk+3.inc | 6 ++-
...Do-not-try-to-initialize-GL-without-libGL.patch | 60 ++++++++++++++++++++++
meta/recipes-gnome/gtk+/gtk+3_3.16.6.bb | 1 +
3 files changed, 66 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-gnome/gtk+/gtk+3/Do-not-try-to-initialize-GL-without-libGL.patch
--
2.1.4
next reply other threads:[~2015-10-21 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:34 Jussi Kukkonen [this message]
2015-10-21 8:34 ` [PATCH 1/1] gtk+3: Do not try to initialize GL without libgl Jussi Kukkonen
2015-10-21 8:43 ` Burton, Ross
2015-10-21 8:53 ` Jussi Kukkonen
2015-10-21 12:36 ` Otavio Salvador
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=cover.1445415749.git.jussi.kukkonen@intel.com \
--to=jussi.kukkonen@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=schnitzeltony@googlemail.com \
/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