]> code.ossystems Code Review - openembedded-core.git/commit
uninative: add variables to the whitelist so that it does not re-triger recipe parsing
authorCuero Bugot <cbugot@sierrawireless.com>
Fri, 16 Mar 2018 17:31:30 +0000 (17:31 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 3 Apr 2018 22:53:13 +0000 (23:53 +0100)
commit75bb95ada98ef129d2fa48568f27dddb078c852c
tree30c91e0162d85f8b698023cdd354157a7dd92084
parent4c2af72f51a7bf187615fc0b3a229d25c3e191e9
uninative: add variables to the whitelist so that it does not re-triger recipe parsing

When uninative is activated (poky's default) internal datastore variables are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative
support. This is happening after parsing is done at the beginning of the build. On the next bitbake call the recipe would be parsed if the two
variables above were not added to the parsing whitelist BB_HASHCONFIG_WHITELIST.

The fix is to add these two variables to the recipe parsing whitelist BB_HASHCONFIG_WHITELIST, this is done at recipe parsing time, only when
uninative.bbclass is used.

Signed-off-by: Cuero Bugot <cbugot@sierrawireless.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/uninative.bbclass