Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot:  package
Date: Mon, 20 Oct 2008 04:32:26 -0700 (PDT)	[thread overview]
Message-ID: <20081020113226.209193C784@busybox.net> (raw)

Author: jacmet
Date: 2008-10-20 04:32:25 -0700 (Mon, 20 Oct 2008)
New Revision: 23741

Log:
BR2_HAVE_DOCUMENTATION: add option to remove documentation from target

Some packages' install-strip target install quite big documentation,
so create an option to remove it similar to the existing man/info options.

Modified:
   trunk/buildroot/Config.in
   trunk/buildroot/package/Makefile.autotools.in


Changeset:
Modified: trunk/buildroot/Config.in
===================================================================
--- trunk/buildroot/Config.in	2008-10-20 11:32:22 UTC (rev 23740)
+++ trunk/buildroot/Config.in	2008-10-20 11:32:25 UTC (rev 23741)
@@ -348,6 +348,13 @@
 	  If you say n here, your target will not contain any
 	  infopage.
 
+config BR2_HAVE_DOCUMENTATION
+	bool "documentation on the target"
+	help
+	  Leave the documentation on the target.
+	  If you say n here, your target will not contain any
+	  documentation.
+
 config BR2_HAVE_DEVFILES
 	bool "development files in target filesystem"
 	help

Modified: trunk/buildroot/package/Makefile.autotools.in
===================================================================
--- trunk/buildroot/package/Makefile.autotools.in	2008-10-20 11:32:22 UTC (rev 23740)
+++ trunk/buildroot/package/Makefile.autotools.in	2008-10-20 11:32:25 UTC (rev 23741)
@@ -256,6 +256,9 @@
 	$(if $(BR2_HAVE_INFOPAGES),,for d in info share/info; do \
 		rm -rf $(TARGET_DIR)/$$d $(TARGET_DIR)/usr/$$d; \
 	done)
+	$(if $(BR2_HAVE_DOCUMENTATION),,for d in doc share/doc; do \
+		rm -rf $(TARGET_DIR)/$$d $(TARGET_DIR)/usr/$$d; \
+	done)
 	$(Q)mkdir -p $(@D)
 	touch $@
 

             reply	other threads:[~2008-10-20 11:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 11:32 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-05 10:41 [Buildroot] svn commit: trunk/buildroot: package egtvedt at uclibc.org
2008-07-24 13:38 jacmet at uclibc.org
2008-06-01 17:58 antab at uclibc.org
2008-03-12 13:07 ninevoltz at uclibc.org
2008-03-10 15:22 ninevoltz at uclibc.org
2008-03-10 16:24 ` Peter Korsgaard
2008-03-10 20:20   ` Ulf Samuelsson
2008-03-10 20:33     ` Peter Korsgaard
2008-03-10 21:17       ` Ulf Samuelsson
2008-03-10 21:26         ` Peter Korsgaard
2008-03-10 21:32           ` Ulf Samuelsson
2008-03-10 23:24             ` Thiago A. Corrêa
2008-03-11  8:11               ` Ulf Samuelsson
2007-10-18 12:38 ulf at uclibc.org
2007-10-07 18:23 ulf at uclibc.org
2007-10-07 18:20 ` Bernhard Fischer
2007-10-07 22:58   ` Ulf Samuelsson
2007-09-17 21:50 aldot at uclibc.org
2007-07-31 18:06 aldot at uclibc.org
2007-07-20  7:34 ulf at uclibc.org
2007-06-28 10:47 aldot at uclibc.org
2006-07-18 15:59 andersen

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=20081020113226.209193C784@busybox.net \
    --to=jacmet@uclibc.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