From: yann.dirson@blade-group.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] packagegroup-tools-bluetooth: work as advertized on distro without bluez* support
Date: Wed, 17 Oct 2018 17:07:57 +0200 [thread overview]
Message-ID: <20181017150757.14591-1-yann@blade-group.com> (raw)
From: Yann Dirson <yann@blade-group.com>
Otherwise the build fails with:
NOTE: Runtime target '${RDEPENDS_}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${RDEPENDS_}']
This restores some truth in the "Otherwise install nothing" comment in the recipe.
Signed-off-by: Yann Dirson <yann@blade-group.com>
---
.../packagegroups/packagegroup-tools-bluetooth.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb b/meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb
index 0ede5e57b..e81516fef 100644
--- a/meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb
+++ b/meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb
@@ -32,6 +32,8 @@ RDEPENDS_bluez5 = " \
'', d)} \
"
+RDEPENDS_ = ""
+
# Install bluez4 tools or bluez5 tools depending on what is specified in the distro.
# Otherwise install nothing.
RDEPENDS_${PN} = "${RDEPENDS_${BLUEZ}}"
--
2.19.1
next reply other threads:[~2018-10-17 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 15:07 yann.dirson [this message]
2018-10-17 15:26 ` [PATCH] packagegroup-tools-bluetooth: work as advertized on distro without bluez* support Martin Jansa
2018-10-17 15:43 ` Yann Dirson
2018-10-17 15:46 ` Martin Jansa
2018-10-17 15:47 ` Yann Dirson
2018-10-17 15:54 ` Martin Jansa
2018-10-17 16:18 ` Yann Dirson
2018-10-17 15:58 ` Mark Hatle
2018-10-17 16:19 ` Yann Dirson
2018-10-17 18:52 ` Martin Jansa
2018-10-17 21:14 ` Yann Dirson
2018-10-17 15:33 ` ✗ patchtest: failure for " Patchwork
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=20181017150757.14591-1-yann@blade-group.com \
--to=yann.dirson@blade-group.com \
--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