From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] utils: Drop is_machine_specific()/machine_path()
Date: Mon, 4 May 2020 16:52:58 +0100 [thread overview]
Message-ID: <20200504155258.3231675-1-richard.purdie@linuxfoundation.org> (raw)
There appear to be no users of these in OE-Core and their functionality
is questionable at best too. Probably safest to remove that entirely
at this point.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/classes/utils.bbclass | 17 -----------------
1 file changed, 17 deletions(-)
diff --git a/meta/classes/utils.bbclass b/meta/classes/utils.bbclass
index c32b868aa88..120bcc64a64 100644
--- a/meta/classes/utils.bbclass
+++ b/meta/classes/utils.bbclass
@@ -1,20 +1,3 @@
-def machine_paths(d):
- """List any existing machine specific filespath directories"""
- machine = d.getVar("MACHINE")
- for basepath in d.getVar("FILESPATHBASE").split(":"):
- machinepath = os.path.join(basepath, machine)
- if os.path.isdir(machinepath):
- yield machinepath
-
-def is_machine_specific(d):
- """Determine whether the current recipe is machine specific"""
- machinepaths = set(machine_paths(d))
- srcuri = d.getVar("SRC_URI").split()
- for url in srcuri:
- fetcher = bb.fetch2.Fetch([srcuri], d)
- if url.startswith("file://"):
- if any(fetcher.localpath(url).startswith(mp + "/") for mp in machinepaths):
- return True
oe_soinstall() {
# Purpose: Install shared library file and
--
2.25.1
next reply other threads:[~2020-05-04 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:52 Richard Purdie [this message]
2020-05-04 16:02 ` ✗ patchtest: failure for utils: Drop is_machine_specific()/machine_path() Patchwork
2020-05-04 16:03 ` [OE-core] [PATCH] " Peter Kjellerstedt
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=20200504155258.3231675-1-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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