Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] force buildroot to regenerate the output/target directory tree
Date: Mon, 25 Feb 2013 15:16:37 +0100	[thread overview]
Message-ID: <20130225151637.078e3155@skate> (raw)
In-Reply-To: <loom.20130225T144049-821@post.gmane.org>

Dear Francesco Montorsi,

On Mon, 25 Feb 2013 13:46:00 +0000 (UTC), Francesco Montorsi wrote:

> I've been using buildroot since some time and there is a thing I
> didn't figure out yet. Consider this situation: I have a working
> buildroot environment; I have copied into the output/target folder
> some stuff so that when I run "make" buildroot generates for me
> images into output/images which already contain the contents I
> manually copied. Now I would like to "reset" the output/target
> folder, i.e. obtain the buildroot "vanilla" output/target tree and to
> obtian the buildroot vanilla output/images.... how can I do that
> without doing a "make clean" (which requires re-compilation of all
> packages and takes a lot of time)? 
> 
> does a "rm -rf output/target && make" works? 

No, it doesn't work, and as of today, there isn't really a simple and
reliable way of doing that.

How long is your entire build? What is your configuration (post
your .config if possible)? Do you have an external toolchain? Have you
used ccache? Are you perhaps building inside a virtual machine and/or
on a slow laptop?

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-02-25 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 13:46 [Buildroot] force buildroot to regenerate the output/target directory tree Francesco Montorsi
2013-02-25 14:16 ` Thomas Petazzoni [this message]
2013-02-25 19:59   ` Francesco Montorsi
2013-02-25 15:15 ` Jérôme Pouiller
2013-02-25 20:02   ` Francesco Montorsi

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=20130225151637.078e3155@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox