Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Montorsi <francesco.montorsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] force buildroot to regenerate the output/target	directory tree
Date: Mon, 25 Feb 2013 20:02:32 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130225T210005-949@post.gmane.org> (raw)
In-Reply-To: 3428566.nT0fW9ztJD@sagittae

J?r?me Pouiller <jezz@...> writes:
> > does a "rm -rf output/target && make" works?
> As Thomas said, it does not work. But, some unofficial hacks exist:
> 
>   * remove build/.root will force to reinstall skeleton
> 
>   * remove build/*/.stamp_target_installed force reinstall each target package
> 
>   * depending of you toolchain, you can reinstall libc and co by removing
>       # stamps/ext-toolchain-installed (external)
>       # stamps/ct-ng-toolchain-installed (ctng)
>       # target/lib/libc.so.0 (buildroot)
> 
> Remind, there are ton of reasons these tips could do wrong things. The only 
> current official way to rebuild target is "make clean".
> 
Thanks!
I will test this approach next time, after doing a backup copy :)

Anyway I think it would be nice to have an additional target in the buildroot 
Makefile which does the operations above (with possible additional quirks) :)

Francesco

      reply	other threads:[~2013-02-25 20:02 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
2013-02-25 19:59   ` Francesco Montorsi
2013-02-25 15:15 ` Jérôme Pouiller
2013-02-25 20:02   ` Francesco Montorsi [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=loom.20130225T210005-949@post.gmane.org \
    --to=francesco.montorsi@gmail.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