From: Markus Volk <f_l_k@t-online.de>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH] edid-decode: allow to build native variant
Date: Sun, 14 Apr 2024 14:58:05 +0200 [thread overview]
Message-ID: <20240414125805.2253456-1-f_l_k@t-online.de> (raw)
This is a requirement for libdisplay-info and fixes:
Program edid-decode found: NO
If libdisplay-info can provide edid-decode-native it looks like:
libdisplay-info| Program edid-decode found: YES (/home/flk/poky/build-hypr/tmp/work/corei7-64-poky-linux/gamescope/3.14.3/recipe-sysroot-native/usr/bin/edid-decode)
libdisplay-info| Program ./edid-decode-check.sh found: YES (/home/flk/poky/build-hypr/tmp/work/corei7-64-poky-linux/gamescope/3.14.3/git/subprojects/libdisplay-info/test/./edid-decode-check.sh)
libdisplay-info| Program ./edid-print-check.sh found: YES (/home/flk/poky/build-hypr/tmp/work/corei7-64-poky-linux/gamescope/3.14.3/git/subprojects/libdisplay-info/test/./edid-print-check.sh)
libdisplay-info| Program ./edid-decode-diff.sh found: YES (/home/flk/poky/build-hypr/tmp/work/corei7-64-poky-linux/gamescope/3.14.3/git/subprojects/libdisplay-info/test/./edid-decode-diff.sh)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
---
meta-oe/recipes-support/edid-decode/edid-decode_git.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-support/edid-decode/edid-decode_git.bb b/meta-oe/recipes-support/edid-decode/edid-decode_git.bb
index bb8c9de71..6eaec800c 100644
--- a/meta-oe/recipes-support/edid-decode/edid-decode_git.bb
+++ b/meta-oe/recipes-support/edid-decode/edid-decode_git.bb
@@ -14,3 +14,5 @@ S = "${WORKDIR}/git"
do_install() {
oe_runmake 'DESTDIR=${D}' install
}
+
+BBCLASSEXTEND = "native"
--
2.44.0
next reply other threads:[~2024-04-14 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 12:58 Markus Volk [this message]
2024-04-15 11:07 ` [oe] [meta-oe][PATCH] edid-decode: allow to build native variant Ross Burton
2024-04-15 11:32 ` Markus Volk
2024-04-15 11:41 ` Ross Burton
2024-04-15 11:50 ` Markus Volk
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=20240414125805.2253456-1-f_l_k@t-online.de \
--to=f_l_k@t-online.de \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).