From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] linux-custom: Fix provides for custom kernels
Date: Wed, 20 Sep 2023 22:02:25 +0300 [thread overview]
Message-ID: <20230920190225.3110384-1-amikan@ilbers.de> (raw)
There are several binary packages described in control file not
mentioned in PROVIDES for correct dependency resolving by bitbake.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta/recipes-kernel/linux/linux-custom.inc | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index 8b367a2f..b8172d72 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -96,10 +96,15 @@ KAFLAGS ?= "-fdebug-prefix-map=${CURDIR}=."
KERNEL_NAME_PROVIDED ?= "${@ d.getVar('PN').partition('linux-')[2]}"
# Make bitbake know we will be producing linux-image and linux-headers packages
+# Also make it know about other packages from control
python() {
kernel_name = d.getVar("KERNEL_NAME_PROVIDED")
- d.setVar('PROVIDES', 'linux-image-' + kernel_name + ' ' + \
- 'linux-headers-' + kernel_name)
+ distro_arch = d.getVar("DISTRO_ARCH")
+ d.appendVar('PROVIDES', ' linux-image-' + kernel_name)
+ d.appendVar('PROVIDES', ' linux-headers-' + kernel_name)
+ d.appendVar('PROVIDES', ' linux-libc-dev')
+ d.appendVar('PROVIDES', ' linux-libc-dev-' + distro_arch + '-cross')
+ d.appendVar('PROVIDES', ' linux-image-' + kernel_name + '-dbg')
}
def get_kernel_arch(d):
--
2.34.1
next reply other threads:[~2023-09-20 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 19:02 Anton Mikanovich [this message]
2023-09-29 6:44 ` Uladzimir Bely
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=20230920190225.3110384-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