Re: diff between defining a "no-op" task and using [noexec]?

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

On Thu, 2013-10-17 at 08:07 -0400, Robert P. J. Day wrote:
>   using a concrete example, there's this from oe core's
> linux-dummy.bb:
> 
> do_configure() {
>         :
> }
> 
> do_compile () {
>         :
> }
> 
> do_install() {
>         :
> }
> 
>   what is the difference between the above and writing:
> 
> do_configure[noexec] = "1"
> do_compile[noexec] = "1"
> do_install[noexec] = "1"
> 
>   *is* there a difference? if so, does it have to do with the
> processing of other flags for that task?
> 
>   i can see that, technically, the first variation still defines a
> task to be run, while the second specifies that the task *not* be run,
> so i can appreciate that those two operations have different results.

The difference is just that, with the first case bitbake will run the
task, it will do nothing. In the second case, bitbake will not bother
running it at all.

Cheers,

Richard