Skip to contentSkip to conversation

local.conf: fix HOSTTOOLS blocking parsing

PATCH New Paul Eggleton 1 participant 1 message Mar 20, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 local.conf: fix HOSTTOOLS blocking parsing

In OE-Core master, HOSTTOOLS specifies a list of host-side tools to be symlinked into a directory that is placed in a filtered path, so that binaries used from the host are a controlled subset. This variable is acted upon at configuration parse time and if any tools are missing, parsing is terminated.

We're not actually running any tasks, so we won't need to call most of the tools specified by HOSTTOOLS. There is one we definitely do need to run (gcc) so keep that one, but the rest can be moved to HOSTTOOLS_NONFATAL.

---
 conf/local.conf | 7 +++++++
 1 file changed, 7 insertions(+)
conf/local.conf +7 -0
index 5a20371..9fe3851 100644
@@ -10,3 +10,10 @@ MACHINE = "qemux86"
 # OE-Core basic distro configuration
 DISTRO = ""
 
+# We're not doing any building, no need to error on missing host tools,
+# but move them to HOSTTOOLS_NONFATAL just in case any do get called
+# from anonymous python or python expressions
+HOSTTOOLS_NONFATAL := "${@d.getVar('HOSTTOOLS', True) or ''} ${@d.getVar('HOSTTOOLS_NONFATAL', True) or ''}"
+# We do definitely need gcc since populate_sdk_base.bbclass refers to
+# oe.utils.get_gcc_version() in a python expression
+HOSTTOOLS = "gcc"
Signature · 1 line
2.9.3