<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 1, 2016 at 2:27 PM, Christopher Larson <span dir="ltr"><<a href="mailto:kergoth@gmail.com" target="_blank">kergoth@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":11s" class="a3s aXjCH m155a85b9ecb28c46">From: Christopher Larson <<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>><br>
<br>
This adds support for .<a href="http://wks.in" rel="noreferrer" target="_blank">wks.in</a> files as WKS_FILE.<br>
<br>
This is a re-send of the RFC PATCH series as a regular PATCH series, to<br>
attempt to get the feature merged. There's a clear value-add, there were no<br>
major objections to the RFC series, and further improvements can be added on<br>
from here.<br>
<br>
These files are treated as the contents of a bitbake variable, so usual<br>
bitbake variable references are supported. I considered using another<br>
templating mechanism, for example the one used by yocto-layer, but then we'd<br>
end up largely mapping metadata variables to template fields anyway, which is<br>
a pointless indirection. Let bitbake expand the variables directly instead.<br>
<br>
This feature lets us, for example, reference ${APPEND} in --append, and avoid<br>
hardcoding the serial console tty in the wks file, and let the user's changes<br>
to APPEND affect wic the way they do the other image construction mechanisms.<br>
<br>
The template is read in and set in a variable at parse time, so changes to the<br>
variables referenced by the template will result in rebuilding the image.<br></div></blockquote></div><br>v2 changes: simplified by dropping the prefuncs bits.<br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Christopher Larson<br>kergoth at gmail dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div></div>
</div></div>