From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v3 1/6] meta: Move kbuildtarget.bbclass
Date: Fri, 3 May 2024 18:04:59 +0300 [thread overview]
Message-ID: <20240503150504.479387-2-amikan@ilbers.de> (raw)
In-Reply-To: <20240503150504.479387-1-amikan@ilbers.de>
Bitbake commit 'BBHandler: Allow earlier exit for classes not found'
requires classes to present inside meta/classes on parsing stage.
Parsing will be halted due to errors otherwise.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta/{recipes-kernel/linux => }/classes/kbuildtarget.bbclass | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/{recipes-kernel/linux => }/classes/kbuildtarget.bbclass (100%)
diff --git a/meta/recipes-kernel/linux/classes/kbuildtarget.bbclass b/meta/classes/kbuildtarget.bbclass
similarity index 100%
rename from meta/recipes-kernel/linux/classes/kbuildtarget.bbclass
rename to meta/classes/kbuildtarget.bbclass
--
2.34.1
next prev parent reply other threads:[~2024-05-03 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 15:04 [PATCH v3 0/6] Update to Bitbake 2.8 Anton Mikanovich
2024-05-03 15:04 ` Anton Mikanovich [this message]
2024-05-03 15:05 ` [PATCH v3 2/6] meta: Fix network flag setting Anton Mikanovich
2024-05-03 15:05 ` [PATCH v3 3/6] Revert "bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s" Anton Mikanovich
2024-05-03 15:05 ` [PATCH v3 4/6] bitbake: Update to 2.8 release Anton Mikanovich
2024-05-03 15:05 ` [PATCH v3 5/6] bitbake: Downgrade python requirements Anton Mikanovich
2024-05-03 15:05 ` [PATCH v3 6/6] testsuite: Fix task name index in order file Anton Mikanovich
2024-05-17 11:20 ` [PATCH v3 0/6] Update to Bitbake 2.8 Anton Mikanovich
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=20240503150504.479387-2-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