[OE-core] i guess there's no way to *conditionally* add tasks?

[Paul Eggleton]

On Tuesday 05 August 2014 13:28:45 Enrico Scholz wrote:
> "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg at public.gmane.org>
> 
> writes:
> > addtask configure_ptest_base after do_configure before do_compile
> > addtask compile_ptest_base   after do_compile   before do_install
> > addtask install_ptest_base   after do_install   before do_package
> > do_populate_sysroot ...
> > 
> >     # Remove all '*ptest_base' tasks when ptest is not enabled
> >     
> >     if not(d.getVar('PTEST_ENABLED', True) == "1"):
> >         for i in ['do_configure_ptest_base', 'do_compile_ptest_base', 
'do_install_ptest_base']:
> >             bb.build.deltask(i, d)
> >   
> >   so i'm guessing there's no way to conditionally add task(s) to avoid
> > 
> > adding them, only to turn around and delete them, yes?
> 
> I solved similar issues by including files conditionally; e.g. above
> would be
> 
> ---
> ptest_inc = "${@['noop', 'ptest'][d.getVar('PTEST_ENABLED', True) == '1']}"
> include ptest-${ptest_inc}.inc
> 
> --- ptest-ptest.inc ---
> addtask configure_ptest_base after do_configure before do_compile
> addtask compile_ptest_base   after do_compile   before do_install
> addtask install_ptest_base   after do_install   before do_package
> do_populate_sysroot

The point is most of the time you shouldn't need to do this kind of thing 
anymore since the introduction of addtask/deltask python functions.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre