From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Tobias Schaffner <tobias.schaffner@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Anton Mikanovich <amikan@ilbers.de>,
Stefan Koch <stefan-koch@siemens.com>
Subject: [PATCH v2 2/3] linux-kernel: Rename cross-pkgs override to cross-profile-native
Date: Fri, 19 Dec 2025 15:33:10 +0100 [thread overview]
Message-ID: <8ea934b514a250f5d441c6414d83fcd44d90d9fc.1766154791.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1766154791.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
This should make the meaning of the override clearer.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/classes-recipe/linux-kernel.bbclass | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/meta/classes-recipe/linux-kernel.bbclass b/meta/classes-recipe/linux-kernel.bbclass
index e129527e..c8e6773f 100644
--- a/meta/classes-recipe/linux-kernel.bbclass
+++ b/meta/classes-recipe/linux-kernel.bbclass
@@ -110,12 +110,11 @@ KERNEL_NAME_PROVIDED ?= "${@ d.getVar('BPN').partition('linux-')[2]}"
# Determine cross-profile override
python() {
if d.getVar("DISTRO_ARCH") != d.getVar("HOST_ARCH") and bb.utils.to_boolean(d.getVar("ISAR_CROSS_COMPILE")):
- if "class-native" not in d.getVar("OVERRIDES").split(":"):
- # cross compiling
- d.appendVar("OVERRIDES", ":cross-profile")
- else:
+ if "class-native" in d.getVar("OVERRIDES").split(":"):
# generating -cross packages (in HOST_ARCH) from a -native variant
- d.appendVar("OVERRIDES", ":cross-pkgs")
+ d.appendVar("OVERRIDES", ":cross-profile-native")
+ else:
+ d.appendVar("OVERRIDES", ":cross-profile")
}
# Default profiles and provides
@@ -129,9 +128,9 @@ BBCLASSEXTEND:append:cross-profile = " kbuildtarget"
# with the default variant of the recipe
BUILD_PROFILES:cross-profile = "pkg.${BPN}.kernel pkg.${BPN}.cross"
-# -native: kbuild package for host
+# -native: kbuild package for host, in cross variant if needed
BUILD_PROFILES:class-native = "pkg.${BPN}.kbuild"
-BUILD_PROFILES:append:cross-pkgs = " pkg.${BPN}.cross"
+BUILD_PROFILES:append:cross-profile-native = " pkg.${BPN}.cross"
RECIPE_PROVIDES:class-native = " \
linux-headers-${KERNEL_NAME_PROVIDED} \
linux-kbuild-${KERNEL_NAME_PROVIDED}"
--
2.51.0
--
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/8ea934b514a250f5d441c6414d83fcd44d90d9fc.1766154791.git.jan.kiszka%40siemens.com.
next prev parent reply other threads:[~2025-12-19 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 14:33 [PATCH v2 0/3] linux-kernel cross fixes and cleanups 'Jan Kiszka' via isar-users
2025-12-19 14:33 ` [PATCH v2 1/3] linux-kernel: Fix building of linux-libc-dev-*-cross packages 'Jan Kiszka' via isar-users
2025-12-19 14:33 ` 'Jan Kiszka' via isar-users [this message]
2025-12-19 14:33 ` [PATCH v2 3/3] linux-kernel: Fix recipe provides for linux-libc-dev targets 'Jan Kiszka' via isar-users
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=8ea934b514a250f5d441c6414d83fcd44d90d9fc.1766154791.git.jan.kiszka@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=stefan-koch@siemens.com \
--cc=tobias.schaffner@siemens.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