All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Peter Tornel <petertornel@yahoo.com>,
	Gaurang Shastri <gmshastri@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: how to clean all?
Date: Mon, 29 Apr 2013 09:31:16 +0100	[thread overview]
Message-ID: <2405529.Zb3KdaMDbY@helios> (raw)
In-Reply-To: <CAE_REAvejk5Yu-m=grtitHa0pxP=4HKkdNgLS9kvJcDGJSdwwQ@mail.gmail.com>

On Monday 29 April 2013 11:11:56 Gaurang Shastri wrote:
> You can run "bitbake -c clean all" to clean everything or simply you can do
> "rm -rf tmp/" directory and you will start from the beginning :)

"bitbake -c clean all" won't work; the syntax would run -c clean on a recipe 
called "all" (which doesn't exist). You may be thinking of "bitbake -c 
cleanall recipename" which cleans the working directory, sstate packages and 
downloaded files for the specified recipe (but not all recipes).

rm -rf tmp/ within your build directory (in the default configuration) will 
delete the output files but won't touch your configuration. If you want to start 
completely from scratch you would also want to delete the sstate-cache 
directory as well, although under normal circumstances there shouldn't be any 
need to do that since the system will work out what it can re-use from the 
cache and what needs to be rebuilt based on any configuration changes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-04-29  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 14:39 how to clean all? Peter Tornel
2013-04-29  5:41 ` Gaurang Shastri
2013-04-29  8:31   ` Paul Eggleton [this message]

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=2405529.Zb3KdaMDbY@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=gmshastri@gmail.com \
    --cc=petertornel@yahoo.com \
    --cc=yocto@yoctoproject.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.