diff options
author | Christopher Larson <chris_larson@mentor.com> | 2016-07-01 14:27:09 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-07-20 10:24:48 +0100 |
commit | 51cb21fe5f050874d52f5b05a8a1de79ea4ebf2f (patch) | |
tree | aeaa0cbd52d95f6b51b69967bac75e19309fe6cd /meta/recipes-devtools/python-numpy/files/mips64n32/config.h | |
parent | 44f1d3cc613563b8d5be61a2648d0cd336fea728 (diff) | |
download | openembedded-core-51cb21fe5f050874d52f5b05a8a1de79ea4ebf2f.tar.gz openembedded-core-51cb21fe5f050874d52f5b05a8a1de79ea4ebf2f.tar.bz2 openembedded-core-51cb21fe5f050874d52f5b05a8a1de79ea4ebf2f.zip |
image_types.bbclass: support template .wks.in files for wic
These files are treated as the contents of a bitbake variable, so usual
bitbake variable references are supported. I considered using another
templating mechanism, for example the one used by yocto-layer, but then we'd
end up largely mapping metadata variables to template fields anyway, which is
a pointless indirection. Let bitbake expand the variables directly instead.
This feature lets us, for example, reference ${APPEND} in --append, and avoid
hardcoding the serial console tty in the wks file, and let the user's changes
to APPEND affect wic the way they do the other image construction mechanisms.
The template is read in and set in a variable at parse time, so changes to the
variables referenced by the template will result in rebuilding the image.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/python-numpy/files/mips64n32/config.h')
0 files changed, 0 insertions, 0 deletions