From: Paul Mundt <lethal@linux-sh.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "James H. Cloos Jr." <cloos@jhcloos.com>, linux-kernel@vger.kernel.org
Subject: Re: make help ARCH=xx fun
Date: Wed, 25 Feb 2004 13:30:38 -0500 [thread overview]
Message-ID: <20040225183038.GA24041@linux-sh.org> (raw)
In-Reply-To: <20040225180858.GW1052@smtp.west.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Wed, Feb 25, 2004 at 11:08:59AM -0700, Tom Rini wrote:
> I can understand that. How about:
> for board in arch/$(ARCH)/configs/*defconfig; \
> do \
> if [ -f $board ]; then
> ...
> fi
> done
>
Simply just matching on *defconfig should be fine. I already changed this on
matching defconfig-* for sh to get around matching SCCS.
> > Also the "- Build for xxxxx" is not good enough.
>
> Erm, it's usually something descriptive enough, if one is firmiliar with
> the platform / what's intended to build.
>
> > I will try to come up with a patch the uses a file named
> > arch/$(ARCH)/configs/index.txt
>
> The 'issue' with configs/index.txt, I'll wager, is that for every new
> board, that's one more file to modify (and thus possibly conflict on).
>
Agreed. The whole reason I did the automated "- Build for foo" thing is that
it's completely automated, and people building should already know what their
target is (if not, they can look at arch/$(ARCH)/Kconfig and figure it out).
I suppose it's not particularly descriptive, but it seems more sensible to
have an abbreviated help text then none whatsoever.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-25 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 14:26 make help ARCH=xx fun James H. Cloos Jr.
2004-02-22 9:50 ` Sam Ravnborg
2004-02-22 14:28 ` James H. Cloos Jr.
2004-02-24 21:55 ` Tom Rini
2004-02-25 19:00 ` Sam Ravnborg
2004-02-25 18:08 ` Tom Rini
2004-02-25 18:30 ` Paul Mundt [this message]
2004-02-25 18:39 ` Tom Rini
2004-02-25 18:44 ` Paul Mundt
2004-02-25 20:39 ` Sam Ravnborg
2004-02-25 19:45 ` Tom Rini
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=20040225183038.GA24041@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.