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 19:59:42 +0000 (UTC) [thread overview]
Message-ID: <loom.20130225T205428-835@post.gmane.org> (raw)
In-Reply-To: 20130225151637.078e3155@skate
Thomas Petazzoni <thomas.petazzoni@...> writes:
> > 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.
ok... I think it would be nice to add one, though!
> 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?
my build is about 1h on an core i5... yes: I'm using ccache.
Anyway, it's not really a matter of compilation flags / development machine. The
point is that in a development stage I often find myself doing several small
changes in the configuration files and other stuff (in a SVN environment); then
I copy them in the output/target tree... my point is that I would like to be
sure that there are no leftovers from previous cp commands I issued.
Perhaps I can do:
make # in buildroot folder
cp -rf output/target output/targetVANILLA
cp -rf /mystuff output/target
make # to generate images containing my customized stuff in output/images
and then
rm -rf output/target
cp -rf output/targetVANILLA output/target
to start over in the future.
Perhaps skeletons are the most clean way to do that... I will look into it as
soon as I find the time!
THanks,
Francesco
next prev parent reply other threads:[~2013-02-25 19:59 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 [this message]
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=loom.20130225T205428-835@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