From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4 v2] Makefile/mkconfig: read simple board configurations from boards.cfg
Date: Sun, 13 Jun 2010 18:10:06 +0200 [thread overview]
Message-ID: <20100613161006.517EB153659@gemini.denx.de> (raw)
In-Reply-To: <1274995116-8708-5-git-send-email-wd@denx.de>
In message <1274995116-8708-5-git-send-email-wd@denx.de> you wrote:
> Instead of adding explicit build rules for each and every board to the
> top level Makefile (which makes it grow and grow), we now provide a
> simple default rule and extend the "mkconfig" script to read board
> configurations from a plain text file (table), "boards.cfg".
>
> For simple boards it is now sufficient to add a single line of text to
> the "boards.cfg" file, no changes to the top level Makefile are needed
> any more.
>
> To make the table better readable, change the notation for unused
> fields from "NULL" into "-".
>
> Signed-off-by: Wolfgang Denk <wd@denx.de>
> Cc: Peter Tyser <ptyser@xes-inc.com>
> Cc: Mike Frysinger <vapier@gentoo.org>
> ---
> Note:
> I had to disable the simple and very convenient rule
> %: %_config
> $(MAKE)
> in the top level Makefile, because it caused each invocation
> of "make" to fail with an error message:
>
> make: *** No rule to make target `Makefile_config'. Stop.
>
> Fixes welcome!
We're still looking for a clean solution for this problem...
>
> Makefile | 823 ++----------------------------------------------------------
> boards.cfg | 356 ++++++++++++++++++++++++++
> mkconfig | 72 ++++--
> 3 files changed, 431 insertions(+), 820 deletions(-)
> create mode 100644 boards.cfg
Applied to "next" branch.
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
Faith may be defined briefly as an illogical belief in the occurence
of the improbable. - H. L. Mencken
prev parent reply other threads:[~2010-06-13 16:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 0:35 [U-Boot] [PATCH 0/3] Makefile: rework / cleanup Wolfgang Denk
2010-05-16 0:35 ` [U-Boot] [PATCH 1/3] Fix printing of make targets, simplify Makefile Wolfgang Denk
2010-05-16 0:35 ` [U-Boot] [PATCH 2/3] Makefile: simplify handling of build target names Wolfgang Denk
2010-05-19 23:40 ` Mike Frysinger
2010-05-16 0:35 ` [U-Boot] [PATCH 3/3] Makefile: simplify handling of common board configurations Wolfgang Denk
2010-05-18 9:05 ` [U-Boot] [PATCH 0/3] Makefile: rework / cleanup Detlev Zundel
2010-05-27 21:18 ` [U-Boot] [PATCH 0/4 v2] " Wolfgang Denk
2010-05-28 1:38 ` Thomas Chou
2010-05-28 12:19 ` Wolfgang Denk
2010-05-28 13:00 ` Scott McNutt
2010-05-28 14:16 ` Thomas Chou
2010-05-28 14:34 ` Thomas Chou
2010-05-27 21:18 ` [U-Boot] [PATCH 1/4 v2] Fix printing of make targets, simplify Makefile Wolfgang Denk
2010-06-13 16:08 ` Wolfgang Denk
2010-05-27 21:18 ` [U-Boot] [PATCH 2/4 v2] Makefile: simplify handling of build target names Wolfgang Denk
2010-06-13 16:08 ` Wolfgang Denk
2010-05-27 21:18 ` [U-Boot] [PATCH 3/4 v2] Makefile: simplify handling of common board configurations Wolfgang Denk
2010-06-13 16:09 ` Wolfgang Denk
2010-05-27 21:18 ` [U-Boot] [PATCH 4/4 v2] Makefile/mkconfig: read simple board configurations from boards.cfg Wolfgang Denk
2010-05-28 5:13 ` Peter Tyser
2010-05-28 5:32 ` Peter Tyser
2010-06-13 16:10 ` Wolfgang Denk [this message]
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=20100613161006.517EB153659@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