layerindex-web/conf/local.conf
Paul Eggleton 84fb2b1b29 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.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2017-03-20 14:34:08 +13:00

20 lines
825 B
Plaintext

#
# This is a version of local.conf trimmed specially for parsing recipes
# within the OE Layer index update script. Since we're not doing any
# actual building and many variables are defaulted via bitbake.conf or
# the OE-Core basic distro config, we don't need to set very much.
# Just select something basic here:
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"