Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-04-04 Thread Randy MacLeod
On 2018-04-03 10:15 AM, Cuero Bugot wrote: In short the answer is that no, we shouldn't and your patch is the better option. I've queued it in sumo-next. Thanks for figuring it out as it is an annoying problem. Hey no prb ! Given he traffic on this list I understand everyone is busy! Would

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-04-03 Thread Cuero Bugot
> In short the answer is that no, we shouldn't and your patch is the better > option. I've queued it in sumo-next. Thanks for figuring it out as it is an > annoying problem. Hey no prb ! Given he traffic on this list I understand everyone is busy! Would it be possible to add it to rocko-next

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-04-03 Thread Richard Purdie
On Fri, 2018-03-30 at 12:45 +, Cuero Bugot wrote: > > > > > > > > > > > > > On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot > > > rrawireless.com> wrote: > > > > When uninative is activated (poky's default) internal > > > > datastore  > > > > variables are modified

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-03-30 Thread Cuero Bugot
> > > On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot > > > wrote: > > > When uninative is activated (poky's default) internal datastore > > > variables are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) > > > to enable uninative support. This is happening

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-03-19 Thread Cuero Bugot
> > On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot > > wrote: > > When uninative is activated (poky's default) internal datastore variables > > are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative > > support. This is happening after

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-03-19 Thread Cuero Bugot
> > On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot > > wrote: > > When uninative is activated (poky's default) internal datastore variables > > are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative > > support. This is happening after

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-03-16 Thread Khem Raj
On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot wrote: > 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

[OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

2018-03-16 Thread Cuero Bugot
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