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 10:28:41 -0400 [thread overview]
Message-ID: <201109191028.42837.vapier@gentoo.org> (raw)
In-Reply-To: <20110919065435.272F41208F1E@gemini.denx.de>
On Monday, September 19, 2011 02:54:35 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > 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
>
> Why should we do that?
>
> Having all build rules in a single, huge Makefile does not sound like
> something that is desirable (and in this context it does not make any
> difference if the file is actually a concatenation of all these build
> rules, or if it's hidden in a set of [probably even nested] includes).
>
> I'm still a big friend of organizing complex stuff in small,
> hierarchical structured pieces, so I have to u nderstand it only a
> small bit at a time.
>
> Yes, running a number of nested makes may have some performance
> penalty. But frankly: I care a ship about that when I can have the
> sofware design simpler and easier to maintain.
i dont think my proposal will be more complex. however, i do think copying &
pasting almost the same exact lines over and over across literally hundreds of
Makefile's is a broken design.
> > 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.
>
> Keep in mind that you said yourslef we always want to remove _all_
> build results - this includes evne those not "listed as a file to
> buil" for a specific configuration setting.
as i mentioned in another e-mail, you do get access to the complete list
regardless of config. COBJS-$(FOO) evaluates to one of two lists: $(COBJS-y)
or $(COBJS-).
-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/c3698430/attachment.pgp
next prev parent reply other threads:[~2011-09-19 14:28 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
2011-09-19 6:54 ` Wolfgang Denk
2011-09-19 14:28 ` Mike Frysinger [this message]
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=201109191028.42837.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