From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nested Makefiles
Date: Thu, 16 Jun 2011 20:09:23 -0400 [thread overview]
Message-ID: <201106162009.24561.vapier@gentoo.org> (raw)
In-Reply-To: <20110616220307.558C819E5AC5@gemini.denx.de>
On Thursday, June 16, 2011 18:03:07 Wolfgang Denk wrote:
> Simon Glass wrote:
> > Is it possible for U-Boot to use a system similar to Linux from 2.6
> > where it prints out the full pathname of each file it is building, and
> > doesn't change in and out of directories as it builds. Perhaps
> > including the subdirectory Makefiles instead using make -C? I haven't
> > looked at how Linux does it. Is there some reason U-Boot cannot /
> > should not do the same?
>
> Of course we can have that - if somebody submits patches for it.
this sounds ambiguous ... i think you mean "no, this isnt going into u-boot,
but people can submit patches to other projects like GNU make".
-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/20110616/7f705aa7/attachment.pgp
next prev parent reply other threads:[~2011-06-17 0:09 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 [this message]
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
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=201106162009.24561.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