From: "Joshua Watt" <JPEWhacker@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Matt Hoosier <matt.hoosier@garmin.com>,
Joshua Watt <JPEWhacker@gmail.com>
Subject: [oe][meta-oe][PATCH] glmark2: don't build full OpenGL backends by default
Date: Thu, 16 Jul 2020 09:34:41 -0500 [thread overview]
Message-ID: <20200716143441.30357-1-JPEWhacker@gmail.com> (raw)
From: Matt Hoosier <matt.hoosier@garmin.com>
Most embedded GPU's implementations OpenGL include only the OpenGL ES
APIs. Attempting to compile the {x11,wayland,drm}-gl variants of
GLMark fail in those cases.
Signed-off-by: Matt Hoosier <matt.hoosier@garmin.com>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
meta-oe/recipes-benchmark/glmark2/glmark2_git.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-oe/recipes-benchmark/glmark2/glmark2_git.bb b/meta-oe/recipes-benchmark/glmark2/glmark2_git.bb
index 6d20bbdaf..82821ad63 100644
--- a/meta-oe/recipes-benchmark/glmark2/glmark2_git.bb
+++ b/meta-oe/recipes-benchmark/glmark2/glmark2_git.bb
@@ -24,9 +24,9 @@ inherit waf pkgconfig features_check
REQUIRED_DISTRO_FEATURES += "opengl"
-PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'x11-gl x11-gles2', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'wayland opengl', 'wayland-gl wayland-gles2', '', d)} \
- drm-gl drm-gles2"
+PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'x11-gles2', '', d)} \
+ ${@bb.utils.contains('DISTRO_FEATURES', 'wayland opengl', 'wayland-gles2', '', d)} \
+ drm-gles2"
PACKAGECONFIG[x11-gl] = ",,virtual/libgl virtual/libx11"
PACKAGECONFIG[x11-gles2] = ",,virtual/libgles2 virtual/libx11"
--
2.27.0
reply other threads:[~2020-07-16 14:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200716143441.30357-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=matt.hoosier@garmin.com \
--cc=openembedded-devel@lists.openembedded.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.