All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] make clean not so clean
Date: Fri, 1 Feb 2008 09:20:56 +0100	[thread overview]
Message-ID: <20080201082056.GA32415@aon.at> (raw)
In-Reply-To: <1201844203.3526.46.camel@localhost.localdomain>

On Fri, Feb 01, 2008 at 12:36:43AM -0500, Ormund Williams wrote:
>On Thu, 2008-01-31 at 21:02 -0800, jake sullivan wrote:
>> I'm not sure how to go about fixing this, but I have been able to
>> recreate an annoying little bug (that I think is the source of a
>> number of other newb problems).
>> 
>...(snip)...
>> My gut says to update "make clean" to delete all the config files (and
>> basically everything but the source files), but before I put work into
>> making and testing a patch, I want to make sure that is the right
>> approach...
>> 
>Don't know about "Right Appraach", but I just locate my download
>directory outside the Buildroot tree.
>
>Under: Build Options --->
>
>	$(BASE_DIR)/../dl) Download dir

This historical behaviour is indeed annoying. Note that distclean only
deletes the DL_DIR if it is set to the default ("$(BASE_DIR)/dl"). I
usually set it to $(BASE_DIR)/down due to this slightly inconvenient
behaviour.

Changing this behaviour is easy, but how should DL_DIR be cleaned-out?
make dl-clean?
Suggestions for a better name for the target?

  reply	other threads:[~2008-02-01  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  5:02 [Buildroot] make clean not so clean jake sullivan
2008-02-01  5:36 ` Ormund Williams
2008-02-01  8:20   ` Bernhard Fischer [this message]
2008-02-01  9:40     ` Robert P. J. Day
2008-02-01  8:34   ` Robert P. J. Day
2008-02-01  8:46     ` Ormund Williams
2008-02-01  9:15       ` Robert P. J. Day

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=20080201082056.GA32415@aon.at \
    --to=rep.dot.nop@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 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.