From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Documentation support
Date: Thu, 19 Nov 2009 06:47:38 -0600 [thread overview]
Message-ID: <200911190647.40852.minimod@morethan.org> (raw)
In-Reply-To: <200911181711.25352.minimod@morethan.org>
On Wed November 18 2009, Michael S. Zick wrote:
>
> Is there a way to "turn on" the "man" utility in BB
> when the buildroot option to store man pages in the
> target is selected?
>
In answer to my own question. . .
The short answer: Yes
The longer answer:
Signed-off-by: Michael S. Zick <minimod@morethan.org>
diff --git a/Config.in b/Config.in
index 6967d25..da3fc14 100644
--- a/Config.in
+++ b/Config.in
@@ -318,6 +318,16 @@ config BR2_HAVE_MANPAGES
If you say n here, your target will not contain any
manpage.
+config BR2_USE_PACKAGE_BUSYBOX_MAN
+ bool "use Busybox man page reader"
+ depends on BR2_HAVE_MANPAGES
+ default n
+ help
+ Enables the man utility in the BusyBox configuration.
+
+ Not required if your build includes another way to
+ use man pages on the target.
+
config BR2_HAVE_INFOPAGES
bool "infopages on the target"
help
diff --git a/package/busybox/busybox.mk b/package/busybox/busybox.mk
index 187a06a..d207074 100644
--- a/package/busybox/busybox.mk
+++ b/package/busybox/busybox.mk
@@ -77,6 +77,10 @@ ifeq ($(BR2_INET_RPC),y)
else
$(SED) "s/^.*CONFIG_FEATURE_MOUNT_NFS.*/CONFIG_FEATURE_MOUNT_NFS=n/;" $(BUSYBOX_DIR)/.config
endif
+ifeq ($(BR2_USE_PACKAGE_BUSYBOX_MAN),y)
+ # force man utility on
+ $(SED) "s/^.*CONFIG_MAN.*/CONFIG_MAN=y/" $(BUSYBOX_DIR)/.config
+endif
ifeq ($(BR2_PACKAGE_BUSYBOX_MKSTATIC),y)
# force static build on
$(SED) "s/^.*CONFIG_STATIC.*/CONFIG_STATIC=y/" $(BUSYBOX_DIR)/.config
prev parent reply other threads:[~2009-11-19 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 23:11 [Buildroot] Documentation support Michael S. Zick
2009-11-19 12:47 ` Michael S. Zick [this message]
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=200911190647.40852.minimod@morethan.org \
--to=minimod@morethan.org \
--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