From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nested Makefiles
Date: Tue, 21 Jun 2011 00:17:27 +0200 [thread overview]
Message-ID: <20110620221727.BCAFE11EEDB1@gemini.denx.de> (raw)
In-Reply-To: <BANLkTi=SJseedJ=vcWr2i+kAsc8A_4EqATf69+y5SKoQH2fomg@mail.gmail.com>
Dear Simon Glass,
In message <BANLkTi=SJseedJ=vcWr2i+kAsc8A_4EqATf69+y5SKoQH2fomg@mail.gmail.com> you wrote:
>
> >> So yes, patches are welcome, but these should go directly to the make
> >> mailing lists / patch system, see
> >> http://savannah.gnu.org/mail/?group=make
> >
> > not to kick sand just for fun, but this is an example of you getting
> > final veto power. ?this has been requested by many people, and ive
> > seen very few people against it (off the top of my head, i can only
> > recall you, but i havent looked at previous threads to be sure).
> >
> > i'm not saying your logic is without merit, just that in all
> > practicality, i dont think it's going to happen the way you desire.
>
> Great to see the discussion here. My feeling is that the right
> approach is for the subdir Makefiles to be #included so that make can
> operate the way it was originally intended (full tree dependency). We
> don't have the kind of memory limitations that once made the size of
> its dependency table worth worrying about.
Be casreful not to mix topics. Mike's message to which you reply here
has actually asolutely nothing to do with nested or recursive
Makefiles or such. He is referring to the other topic (terse make
output) instead.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
What's the sound a name makes when it's dropped?
next prev parent reply other threads:[~2011-06-20 22:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 14:32 [U-Boot] Nested Makefiles Simon Glass
2011-06-16 22:03 ` Wolfgang Denk
2011-06-16 23:03 ` Måns Rullgård
2011-06-17 0:10 ` Mike Frysinger
2011-06-17 0:09 ` Mike Frysinger
2011-06-18 13:49 ` Albert ARIBAUD
2011-06-18 15:43 ` Rod Boyce
2011-06-18 20:07 ` Wolfgang Denk
2011-06-18 17:42 ` Mike Frysinger
2011-06-18 20:09 ` Wolfgang Denk
2011-06-20 16:32 ` Scott Wood
2011-06-20 19:53 ` Mike Frysinger
2011-06-20 20:30 ` Simon Glass
2011-06-20 22:17 ` Wolfgang Denk [this message]
2011-06-20 23:52 ` Simon Glass
2011-06-21 2:01 ` Mike Frysinger
2011-06-20 22:23 ` 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=20110620221727.BCAFE11EEDB1@gemini.denx.de \
--to=wd@denx.de \
--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