All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: how many ways to delete/de-activate a recipe's task?
Date: Wed, 11 Mar 2015 12:22:50 -0500	[thread overview]
Message-ID: <550079EA.7030500@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1503111228420.5897@localhost>

On 3/11/15 11:30 AM, Robert P. J. Day wrote:
> 
>   i recall that richard purdie might have explained this once but i
> have no idea where that post is and i need to add something to it,
> anyway ... how many ways are there to "delete" a task from a recipe,
> and what are the differences?
> 
>   so far, i've seen:
> 
> 1) bitbake supports a "deltask" directive

The task and all it's dependencies go away.  So anything dependent on it and the
things it depends on, are no longer dependent.

> 2) you can use the [noexec] task flag

The task and it's dependencies remain, but nothing is executed.

> 3) i've also seen redefining the task with a no-op ":" command

The task is executed and does nothing.  (I believe this dumps a stamp file and
the noexec does not.. but I may be wrong.)

--Mark

>   so what are the differences, and when would someone use one over the
> others? thanks.
> 
> rday
> 



  reply	other threads:[~2015-03-11 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:30 how many ways to delete/de-activate a recipe's task? Robert P. J. Day
2015-03-11 17:22 ` Mark Hatle [this message]
2015-03-11 17:57   ` Richard Purdie
2015-03-12  7:52     ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=550079EA.7030500@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.