Re: [yocto] variable and task/function timing

["Trevor Woerner" <twoerner@gmail.com>]

On Wed 2019-12-11 @ 03:48:51 PM, Richard Purdie wrote:
> On Wed, 2019-12-11 at 10:39 -0500, Trevor Woerner wrote:
> > On Wed 2019-12-11 @ 11:06:44 AM, Nicolas Dechesne wrote:
> > > >         +python do_check_build_type() {
> > > >         +    _buildtype = d.getVar('MESA_BUILD_TYPE')
> > > >         +    if _buildtype not in ['release', 'debug']:
> > > >         +        bb.fatal("unknown build type (%s), please set to
> > > > either 'release' or 'debug'" % _buildtype)
> > > >         +    if _buildtype == 'debug':
> > > >         +        d.setVar('MESON_BUILDTYPE', 'debugoptimized')
> > > >         +        bb.plain("setting meson build type to
> > > > debugoptimized")
> > > >         +}
> > > >         +addtask check_build_type before do_configure
> > > >         +
> > > >          EXTRA_OEMESON = " \
> > > >              -Dshared-glapi=true \
> > > >              -Dgallium-opencl=disabled \
> > 
> > Whether I move the above to before or after the "inherit meson..."
> > line makes no difference. Probably because the variable is being set
> > by a task (which, I assume, is too late to have any effect, which is
> > a large part of why I wrote this email: when do these tasks get
> > called with respect to how variable are being set by all the
> > different ways they're being set?)
> 
> Tasks run in isolation, if you change the datastore in a task it has no
> way to get "seen" by other tasks. They're separate processes.
> 
> That is why the setVar in a task has no effect outside that task.

Excellent, that explains a lot, thanks!

So in this case, the answer to the question of "when" is: never :-)