From: Tom Rini <trini@kernel.crashing.org>
To: "James H. Cloos Jr." <cloos@jhcloos.com>, linux-kernel@vger.kernel.org
Subject: Re: make help ARCH=xx fun
Date: Wed, 25 Feb 2004 11:08:59 -0700 [thread overview]
Message-ID: <20040225180858.GW1052@smtp.west.cox.net> (raw)
In-Reply-To: <20040225190049.GB2474@mars.ravnborg.org>
On Wed, Feb 25, 2004 at 08:00:49PM +0100, Sam Ravnborg wrote:
> >
> > Hmm. Would something (untested) like the following be horribly
> > wrong/bad?
> >
> > define archhelp
> > @echo ' zImage - Compressed kernel image (arch/sh/boot/zImage)'
> > @if [ -d arch/$(ARCH)/configs/SCCS ]; then bk get -q arch/$(ARCH)/configs/;fi
> > # Assume board_defconfig
> > for board in arch/$(ARCH)/configs/*defconfig; \
> > do \
> > echo -n ' ' $$board | sed -e 's|arch/$(ARCH)/configs/||g' ; \
> > echo -n ' - Build for ' ; \
> > echo -e $$board | sed -e 's|.*_||g'; \
> > done
> > endef
>
> I do not want kbuild to be cluttered with bk specific stuff.
I can understand that. How about:
for board in arch/$(ARCH)/configs/*defconfig; \
do \
if [ -f $board ]; then
...
fi
done
> 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).
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-25 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 14:26 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 [this message]
2004-02-25 18:30 ` Paul Mundt
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=20040225180858.GW1052@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®