From: <rs@ti.com>
To: <detheridge@ti.com>, <denys@konsulko.com>, <reatmon@ti.com>
Cc: <meta-arago@lists.yoctoproject.org>
Subject: [meta-arago][kirkstone/master][PATCH] arago.conf: remove x11 again
Date: Thu, 1 Feb 2024 10:55:37 -0600 [thread overview]
Message-ID: <20240201165537.3874417-1-rs@ti.com> (raw)
From: Randolph Sapp <rs@ti.com>
We don't support x11, and while it can currently be enabled in tandem
with our graphics stack right now without explicitly causing issues on
it's own, Yocto still treats the presence of x11 as a distro feature to
mean that desktop GL is present.
This assumption leads to a lot of incorrectly configured packages in our
case so to prevent future incompatibility with layers adjusting their
PACKAGECONFIG values with this logic we should explicitly remove x11
again.
This decision will likely flip again if oe-core introduces a standard
"opengles" feature instead of just the blanket "opengl" one they
currently use.
Signed-off-by: Randolph Sapp <rs@ti.com>
---
This has a dependency on the following patch in meta-ti since vulkan is
currently enabled:
https://lists.yoctoproject.org/g/meta-ti/message/17432
meta-arago-distro/conf/distro/arago.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf
index ecbcbf1a..2a2b827f 100644
--- a/meta-arago-distro/conf/distro/arago.conf
+++ b/meta-arago-distro/conf/distro/arago.conf
@@ -47,6 +47,7 @@ DISTRO_FEATURES = "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
# Add additional distro features
DISTRO_FEATURES:append = " pam wayland opengl"
+DISTRO_FEATURES:remove = "x11"
#DISTRO_FEATURES:append = " opencl"
DISTRO_FEATURES:append = " vulkan"
DISTRO_FEATURES:append = " opencv"
--
2.43.0
reply other threads:[~2024-02-01 16:55 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=20240201165537.3874417-1-rs@ti.com \
--to=rs@ti.com \
--cc=denys@konsulko.com \
--cc=detheridge@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).