From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] punt unused clean/distclean targets
Date: Mon, 19 Sep 2011 01:32:27 -0400 [thread overview]
Message-ID: <201109190132.29081.vapier@gentoo.org> (raw)
In-Reply-To: <CALButC+_dvp3YY6eUNdboktq72MbOq1TN6jEUX5nvL+VByvSAA@mail.gmail.com>
On Monday, September 19, 2011 01:11:17 Graeme Russ wrote:
> Hi Mike
>
> On Mon, Sep 19, 2011 at 2:59 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Sunday, September 18, 2011 09:08:35 Graeme Russ wrote:
> >> On 18/09/11 18:22, Mike Frysinger wrote:
> >> > On Sunday, September 18, 2011 03:26:38 Wolfgang Denk wrote:
> >> >> Mike Frysinger wrote:
> >> >>> The top level Makefile does not do any recursion into subdirs when
> >> >>> cleaning, so these clean/distclean targets in random arch/board dirs
> >> >>> never get used. Punt them all.
>
> [snip]
>
> >> Can we not have make distclean/mrproper traverse ALL arch/SoC/board
> >> directories and call their distclean/mrproper? Or have
> >> distclean/mrproper read the .mk file for all arch/SoC/board
> >> directories?
> >
> > if it wasn't clear in my last e-mail, i want to move in the direction of
> > .mk files that the top level would include them and thus all the
> > specific cruft would be kept there
> >
> > after all, the list of things to clean should be obvious once we have
> > more kbuild style system: if it's listed as a file to build, then it
> > should get cleaned.
>
> 'make distclean' and 'make mrproper' should delete ALL intermediate build
> files and basically return the local git repository to the same state that
> it would be in if you did a fresh git-clone regardless of what config
> options git set.
yes. i dont believe i said anything differently.
remember that just because you have COBJS-$(FOO) doesnt mean you need FOO to
be defined to have access to that item. you can just as easily do `rm -f
$(COBJS-) $(COBJS-y)`.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110919/5fec8e57/attachment.pgp
next prev parent reply other threads:[~2011-09-19 5:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 5:17 [U-Boot] [PATCH] punt unused clean/distclean targets Mike Frysinger
2011-09-18 7:26 ` Wolfgang Denk
2011-09-18 8:22 ` Mike Frysinger
2011-09-18 13:08 ` Graeme Russ
2011-09-19 4:59 ` Mike Frysinger
2011-09-19 5:10 ` Marek Vasut
2011-09-19 5:30 ` Mike Frysinger
2011-09-19 6:57 ` Wolfgang Denk
2011-09-19 5:11 ` Graeme Russ
2011-09-19 5:32 ` Mike Frysinger [this message]
2011-09-19 6:54 ` Wolfgang Denk
2011-09-19 14:28 ` Mike Frysinger
2011-09-19 18:29 ` Scott Wood
2011-09-19 20:57 ` [U-Boot] serial ifdef mess Mike Frysinger
2011-09-20 0:41 ` Graeme Russ
2011-09-20 0:52 ` Mike Frysinger
2011-09-20 1:07 ` Graeme Russ
2011-09-20 4:28 ` Simon Glass
2011-09-20 4:44 ` Mike Frysinger
2011-09-20 5:12 ` Graeme Russ
2011-09-20 7:29 ` Wolfgang Denk
2011-09-20 4:40 ` Mike Frysinger
2011-10-13 16:54 ` [U-Boot] [PATCH v2] punt unused clean/distclean targets Mike Frysinger
2011-10-15 20:20 ` Wolfgang Denk
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=201109190132.29081.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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