path: root/meta/conf/bitbake.conf
diff options
authorMax Eliaser <max.eliaser@intel.com>2014-06-10 13:24:16 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-06-13 12:28:16 +0100
commit160087f754eabf5da90fb51997e19d2e585aac4a (patch)
treeb858ff9cea5fdca2f8118e083c3a3741f7cab843 /meta/conf/bitbake.conf
parent0d8d5a2d44988d32a5c8b995202a12ac106ba93c (diff)
texinfo.bbclass: native/cross uses dummy texinfo; target uses host's Texinfo.
To unpack that to more than a single line: -native and -cross recipes are made to use the dummy Texinfo utilities provided by texinfo-dummy-native if they invoke those utilities at build time. The target-architecture (cross-compiled) recipes still use the genuine Texinfo utilites. Right now, they still use the host system's Texinfo utilities, but could be made to use the texinfo-native recipe we already ship with some config file changes. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/bitbake.conf')
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 1d70d3c9dd..cd6f94004e 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -181,6 +181,7 @@ ASSUME_PROVIDED = "\
python-native-runtime \
tar-native \
virtual/libintl-native \
+ texinfo-native\
# gzip-native should be listed above?