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: Tue, 24 Feb 2004 14:55:48 -0700 [thread overview]
Message-ID: <20040224215548.GF1052@smtp.west.cox.net> (raw)
In-Reply-To: <20040222095021.GB2266@mars.ravnborg.org>
On Sun, Feb 22, 2004 at 10:50:21AM +0100, Sam Ravnborg wrote:
> On Sat, Feb 21, 2004 at 09:26:41AM -0500, James H. Cloos Jr. wrote:
> > I was looking at the arch-specific make options for various archs,
> > and found this bit of fun:
> >
> > :; make help ARCH=sh
> > [elided]
> > Architecture specific targets (sh):
> > zImage - Compressed kernel image (arch/sh/boot/zImage)
> > SCCS - Build for arch/sh/configs/SCCS
> > defconfig-adx - Build for adx
> > defconfig-cqreek - Build for cqreek
> > defconfig-dreamcast - Build for dreamcast
> > defconfig-hp680 - Build for hp680
> > defconfig-se7751 - Build for se7751
> > defconfig-snapgear - Build for snapgear
> > defconfig-systemh - Build for systemh
> > [elided]
> >
> > The defconfig options only show up after a bk get in arch/sh/configs/.
> The sh people have decided to create the list based on the content of the directory.
> Therefore you see the SCCS entry, and that's why you need to do a 'bk bet'.
> In general you cannot expect the konfig and build system to work 100% if there is
> random files missing in the tree. Those files bk can checkout automatically is
> more by luck - and no effort has been put into making this a trustworthy way
> to do it.
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 kinda like the idea of documenting the various defconfig targets, in
make help, so maybe even adding that to the normal help section iff
arch/$(ARCH)/configs exists... Thoughts?
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-24 21:55 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 [this message]
2004-02-25 19:00 ` Sam Ravnborg
2004-02-25 18:08 ` Tom Rini
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=20040224215548.GF1052@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®