[OE-core] uninative and recipe parsing

2018-03-12 Thread Cuero Bugot
Hi all, When you add several layers, recipe parsing can take a (very) long time. In our case it takes more than a couple minutes [1]. Fortunately it is supposed to happens once, except when you use uninative (poky's default) where it happens twice (the two first times you build). I think this

[OE-core] [PATCH] Fetch uninative binaries before recipe are parsed so that the datastore variables are updated and recipes parsed accordingly.

2018-03-13 Thread Cuero Bugot
). And the uninative variables are set to the correct values for recipe parsing. Note: it also saves a second complete parsing the second time you run bitbake. Signed-off-by: Cuero Bugot <cbu...@sierrawireless.com> --- meta/classes/uninative.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 de

Re: [OE-core] uninative and recipe parsing

2018-03-13 Thread Cuero Bugot
> I have kind of noticed this and agree its something we should fix. > Thanks for digging into it. I think a long time ago we tried the above change > and it does cause a problem, perhaps fetching during parsing which is bad. > > Have you been able to figure out what changes in the data store

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 > > > <mailto:cbu...@sierrawireless.com> wrote: > > > When uninative is activated (poky's default) internal datastore > > > variables are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) > >

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

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

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

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 > > <mailto:cbu...@sierrawireless.com> wrote: > > When uninative is activated (poky's default) internal datastore variables > > are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative > &

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 > > <mailto:cbu...@sierrawireless.com> wrote: > > When uninative is activated (poky's default) internal datastore variables > > are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative > &