From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 4/5] texinfo: Only build texinfo when api-docs enabled
Date: Tue, 28 Jan 2020 15:16:42 +0000 [thread overview]
Message-ID: <20200128151643.9711-4-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20200128151643.9711-1-richard.purdie@linuxfoundation.org>
Also fix the crosssdk and cross-canadian cases.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/classes/texinfo.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/texinfo.bbclass b/meta/classes/texinfo.bbclass
index 72091c733e5..ba1dd4994e1 100644
--- a/meta/classes/texinfo.bbclass
+++ b/meta/classes/texinfo.bbclass
@@ -6,9 +6,11 @@
# Texinfo recipe, you can remove texinfo-native from ASSUME_PROVIDED and
# makeinfo from SANITY_REQUIRED_UTILITIES.
-TEXDEP = "texinfo-native"
+TEXDEP = "${@bb.utils.contains('DISTRO_FEATURES', 'api-documentation', 'texinfo-native', 'texinfo-dummy-native', d)}"
TEXDEP_class-native = "texinfo-dummy-native"
TEXDEP_class-cross = "texinfo-dummy-native"
+TEXDEP_class-crosssdk = "texinfo-dummy-native"
+TEXDEP_class-cross-canadian = "texinfo-dummy-native"
DEPENDS_append = " ${TEXDEP}"
# libtool-cross doesn't inherit cross
--
2.20.1
next prev parent reply other threads:[~2020-01-28 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:16 [PATCH 1/5] bc: Use texinfo class Richard Purdie
2020-01-28 15:16 ` [PATCH 2/5] glibc-package.inc: Remove warnings about unpacked directories Richard Purdie
2020-01-28 15:16 ` [PATCH 3/5] texinfo/texinfo-dummy-native: Drop native path prefix Richard Purdie
2020-01-29 2:00 ` Khem Raj
2020-01-29 11:59 ` Richard Purdie
2020-01-29 16:02 ` Khem Raj
2020-01-28 15:16 ` Richard Purdie [this message]
2020-01-28 15:16 ` [PATCH 5/5] bitbake.conf/sanity: Drop makeinfo as being required on buildhost Richard Purdie
2020-01-28 15:58 ` [PATCH 1/5] bc: Use texinfo class Jacob Kroon
2020-01-28 16:18 ` Richard Purdie
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=20200128151643.9711-4-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