Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] *clean targets
Date: Fri, 09 Oct 2009 13:28:04 +0200	[thread overview]
Message-ID: <87my40hkmz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20091009094809.GH2266@mx.loc> (Bernhard Reutner-Fischer's message of "Fri\, 9 Oct 2009 11\:48\:09 +0200")

>>>>> "Bernhard" == Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> writes:

Hi,

 >> * On the clean target
 >> 
 >> I see that all the stamps are removed. So this will trigger
 >> basically a reconfigure + rebuild of all packages. Is this what we
 >> want ?

 Bernhard> yes, this is what i as a user would expect.
 Bernhard> Something broke, i have to rebuild stuff, so i
 Bernhard> make clean ; make

So in other words, we should just have clean and distclean, where the
only difference between those two is that clean doesn't delete your
.config?

 >> Same question as before: is removing the target/ directory without
 >> removing the staging/ directory really safe ?
 >> 
 >> Removing $(IMAGE) will not do anything, since $(IMAGE) is the prefix
 >> for the filesystem images. I.e, the tar image is $(IMAGE).tar.

 Bernhard> the IMAGE was there already. Ask Ulf what it was ment to be.

Ok, but lets really fix up stuff now that we're changing these things.


 >> Shouldn't we just remove $(BINARIES_DIR) ?

 Bernhard> works for me, but they have to be regenerated anyway, so not
 Bernhard> much point, i'd say.

They should imho get removed so the user doesn't get confused if the
build fails, but they still see (old) binaries in BINARIES_DIR.

But ok, moot point if we make clean remove everything.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-10-09 11:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 16:24 [Buildroot] [RFC] *clean targets Bernhard Reutner-Fischer
2009-10-07 16:32 ` Sven Neumann
2009-10-07 18:12   ` Peter Korsgaard
2009-10-07 18:25     ` Bernhard Reutner-Fischer
2009-10-07 18:26 ` Peter Korsgaard
2009-10-07 18:31   ` Bernhard Reutner-Fischer
2009-10-07 19:31     ` Peter Korsgaard
2009-10-09  8:01     ` Thomas Petazzoni
2009-10-07 18:27 ` Peter Korsgaard
2009-10-09  7:51 ` Thomas Petazzoni
2009-10-09  8:00   ` Thomas Petazzoni
2009-10-09  9:48     ` Bernhard Reutner-Fischer
2009-10-09 11:28       ` Peter Korsgaard [this message]
2009-11-20 13:04         ` Peter Korsgaard
2009-11-20 15:28           ` Bernhard Reutner-Fischer
2009-11-20 15:55             ` Peter Korsgaard
2009-11-20 16:19             ` Bernhard Reutner-Fischer
2009-11-20 16:20               ` Peter Korsgaard

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=87my40hkmz.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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