From: jasper@fancydomain.eu
To: openembedded-core@lists.openembedded.org
Cc: martin@mko.dev, Daniel.Baumgart@iris-sensing.com,
bitbake-devel@lists.openembedded.org,
Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>
Subject: [oe-core][PATCH v4 2/2] base.bbclass: Add sysroot deps for repo fetcher
Date: Wed, 10 Nov 2021 16:53:32 +0100 [thread overview]
Message-ID: <20211110155332.578088-2-jasper@fancydomain.eu> (raw)
In-Reply-To: <20211110155332.578088-1-jasper@fancydomain.eu>
From: Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>
Add git-native and repo-native as prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>
---
meta/classes/base.bbclass | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index a65fcc6c1d..3298bd1952 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -665,6 +665,11 @@ python () {
elif uri.scheme == "npm":
d.appendVarFlag('do_fetch', 'depends', ' nodejs-native:do_populate_sysroot')
+ elif uri.scheme == "repo":
+ needsrcrev = True
+ d.appendVarFlag('do_fetch', 'depends', ' repo-native:do_populate_sysroot')
+ d.appendVarFlag('do_fetch', 'depends', ' git-native:do_populate_sysroot')
+
# *.lz4 should DEPEND on lz4-native for unpacking
if path.endswith('.lz4'):
d.appendVarFlag('do_unpack', 'depends', ' lz4-native:do_populate_sysroot')
--
2.33.1
next prev parent reply other threads:[~2021-11-10 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 15:53 [oe-core][PATCH v4 1/2] repo: Add recipe for 2.17.3 jasper
2021-11-10 15:53 ` jasper [this message]
2021-11-10 15:56 ` [oe-core][PATCH v4 2/2] base.bbclass: Add sysroot deps for repo fetcher Jasper Orschulko
2021-11-10 17:20 ` [bitbake-devel] [oe-core][PATCH v4 1/2] repo: Add recipe for 2.17.3 Khem Raj
2021-11-11 10:26 ` Jasper Orschulko
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=20211110155332.578088-2-jasper@fancydomain.eu \
--to=jasper@fancydomain.eu \
--cc=Daniel.Baumgart@iris-sensing.com \
--cc=Jasper.Orschulko@iris-sensing.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=martin@mko.dev \
--cc=openembedded-core@lists.openembedded.org \
/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