From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package help targets help-all
Date: Wed, 13 Aug 2008 12:43:56 -0700 [thread overview]
Message-ID: <1218656636.6490.15.camel@kokopelli> (raw)
This patch will add the target "help-all" which depends on
$(HELP_TARGETS) which is set in the previous two patches I sent. If
this patch is accepted I can do patches for other packages.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
Brian Beattie LFS12947 | "Honor isn't about making the right choices.
beattie at beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net | -- Midori Koto
------------------------------- patch
----------------------------------Index: Makefile
===================================================================
--- Makefile (revision 23076)
+++ Makefile (working copy)
@@ -26,6 +26,7 @@
CONFIG_DEFCONFIG=.defconfig
CONFIG=package/config
DATE:=$(shell date +%Y%m%d)
+HELP_TARGETS:=help
noconfig_targets:=menuconfig config oldconfig randconfig \
defconfig allyesconfig allnoconfig release tags \
@@ -251,6 +252,7 @@
ifeq ($(BR2_PACKAGE_LINUX),y)
TARGETS+=linux26-modules
+HELP_TARGETS+=linux26-help
endif
include package/*/*.mk
@@ -507,9 +509,14 @@
@echo ' source-check - check all packages for valid
download URLs'
@echo ' external-deps - list external packages used'
@echo
+ @echo ' help-all - list package help'
+ @echo
@echo 'See docs/README and docs/buildroot.html for further details'
@echo
+help-all: $(HELP_TARGETS)
+
.PHONY: dummy subdirs release distclean clean config oldconfig \
- menuconfig tags check test depend defconfig help
+ menuconfig tags check test depend defconfig help \
+ help-all $(HELP_TARGETS)
reply other threads:[~2008-08-13 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1218656636.6490.15.camel@kokopelli \
--to=beattie@beattie-home.net \
--cc=buildroot@busybox.net \
/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