From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add help target to Makefile.in.advanced
Date: Wed, 13 Aug 2008 12:38:15 -0700 [thread overview]
Message-ID: <1218656295.6490.6.camel@kokopelli> (raw)
This patch adds the target "linux26-help" which will list the targets
available, because I can never keep track of them.
--
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: target/linux/Makefile.in
===================================================================
--- target/linux/Makefile.in (revision 23076)
+++ target/linux/Makefile.in (working copy)
@@ -246,3 +246,23 @@
rm -rf $(LINUX26_DIR)
endif
+
+linux26-help:
+ @echo
+ @echo "==================="
+ @echo "linux26 targets"
+ @echo
+ @echo "linux26-menuconfig - Run menuconfig for kernel"
+ @echo "linux26-xconfig - Run xconfig for kernel"
+ @echo "linux26 - Make kernel"
+ @echo "linux26-modules - Make kernel modules"
+ @echo "linux26-source - Get kernel source distribution"
+ @echo "linux26-unpacked - Unpack kernel source and apply patches"
+ @echo "linux26-config - Configure kernel"
+ @echo "linux26-update - Save current kernel configuration"
+ @echo "linux26-force - Force complete kernel build on next \"make
\""
+ @echo "linux26clean - Mark kernel source unconfigured and run
\"make clean\""
+ @echo "linux26-dirclean - Remove kernel source directory"
+ @echo
+
+HELP_TARGETS+=linux26-help
reply other threads:[~2008-08-13 19:38 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=1218656295.6490.6.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