Re: Removing do_compile task and ordering problem

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2015-05-21 at 13:55 +0100, Paul Eggleton wrote:
> Hi Marcin,
> 
> On Thursday 21 May 2015 12:47:05 Marcin Krzemiński wrote:
> > I am writing recipe that inherits from *native*.
> > I removed do_compile task using: *deltask do_compile*
> > When i was ruing bitbake my-recipe all works fine, but when I added recipe
> > to *EXTRA_IMAGEDEPENDS *and run* bitbake core-image-minimal *tasks were
> > reordered in some strange way that task do_install was performed before
> > do_fetch.
> > When I hanged *deltask do_compile *to *do_compile[noexec] = "1" * all went
> > back to normal.
> > I found *deltask *in manual so I do not know, is it a bug or not?
> 
> I suspect this is because all deltask does is delete the task, it does not 
> reconnect the dependency chain such that tasks that depended on the deleted 
> task would depend on the tasks that the deleted task depended upon, so what 
> you get in this case is do_install no longer having any dependencies. To be 
> honest the current behaviour seems reasonable to me, though it is not 
> immediately obvious and ought to be described in the manual. I think in your 
> situation you really do want to set the noexec flag rather than using deltask.

Correct, this is basically the difference between deltask and noexec.
noexec has the behaviour you want in this case and we should clarify in
the manual.

Cheers,

Richard