public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2] linux-custom: Sync provides value with build profiles
Date: Mon, 10 Nov 2025 16:53:15 +0200	[thread overview]
Message-ID: <20251110145315.333626-1-amikan@ilbers.de> (raw)

Packages linux-libc-dev and linux-libc-dev-${DISTRO_ARCH}-cross were
added to PROVIDES variable unconditionally, while those packages are
not really built until KERNEL_LIBC_DEV_DEPLOY enabled (which is set to
"0" by default).

Add libc-dev packages to PROVIDES only if there are no 'nolibcdev'
Debian build profile used so PROVIDES will be always in sync with real
set of packages being built.

Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
Changes in v2:
- Rebase on collision fixes in next.
- Migrate implementation to overrides.

 meta/recipes-kernel/linux/linux-custom.inc | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index 9dd9abb5..5071367d 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -156,12 +156,19 @@ ISAR_CROSS_COMPILE:class-kbuildtarget = "0"
 RECIPE_PROVIDES = " \
     linux-image-${KERNEL_NAME_PROVIDED} \
     linux-headers-${KERNEL_NAME_PROVIDED} \
-    linux-libc-dev \
-    linux-libc-dev-${DISTRO_ARCH}-cross \
     linux-image-${KERNEL_NAME_PROVIDED}-dbg \
     linux-kbuild-${KERNEL_NAME_PROVIDED} \
     ${BPN}-pseudo-native \
 "
+
+# Provide linux-libc-dev packages unless nolibcdev profile used
+OVERRIDES:append = ":${@ bb.utils.contains('DEB_BUILD_PROFILES', 'pkg.{}.nolibcdev'.format(d.getVar('BPN')), 'nolibcdev', 'libcdev', d)}"
+
+RECIPE_PROVIDES:append:libcdev = " \
+    linux-libc-dev \
+    linux-libc-dev-${DISTRO_ARCH}-cross \
+"
+
 # When cross-profile is active:
 # kbuild package is provided by -native or -kbuildtarget variant. Also headers
 # provisioning moves over to ensure those variants are pulled, although the
-- 
2.34.1

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20251110145315.333626-1-amikan%40ilbers.de.

                 reply	other threads:[~2025-11-10 14:53 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=20251110145315.333626-1-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.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