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/pcre
Date: Sat, 16 Aug 2008 12:36:37 -0700 (PDT)	[thread overview]
Message-ID: <20080816193637.0E5DF3C7BC@busybox.net> (raw)

Author: jacmet
Date: 2008-08-16 12:36:36 -0700 (Sat, 16 Aug 2008)
New Revision: 23094

Log:
pcre: fix target install

Use install-strip and clean up documentation files instead of
install-exec so files get stripped and manpages installed if
requested.

Modified:
   trunk/buildroot/package/pcre/pcre.mk


Changeset:
Modified: trunk/buildroot/package/pcre/pcre.mk
===================================================================
--- trunk/buildroot/package/pcre/pcre.mk	2008-08-16 19:13:53 UTC (rev 23093)
+++ trunk/buildroot/package/pcre/pcre.mk	2008-08-16 19:36:36 UTC (rev 23094)
@@ -8,6 +8,7 @@
 PCRE_SITE = ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre
 PCRE_INSTALL_STAGING = YES
 PCRE_INSTALL_TARGET = YES
+PCRE_INSTALL_TARGET_OPT:=DESTDIR=$(TARGET_DIR) install-strip
 
 ifneq ($(BR2_INSTALL_LIBSTDCPP),y)
 # pcre will use the host g++ if a cross version isn't available
@@ -17,3 +18,7 @@
 PCRE_DEPENDENCIES = uclibc
 
 $(eval $(call AUTOTARGETS,package,pcre))
+
+$(PCRE_HOOK_POST_INSTALL): $(PCRE_TARGET_INSTALL_TARGET)
+	rm -rf $(TARGET_DIR)/usr/share/doc/pcre
+	touch $@

             reply	other threads:[~2008-08-16 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 19:36 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-17 21:33 [Buildroot] svn commit: trunk/buildroot/package/pcre jacmet at uclibc.org
2008-09-18 10:28 ` Daniel Laird
2008-09-18 10:34   ` Peter Korsgaard
2008-08-16 12:32 jacmet at uclibc.org
2008-08-16 12:32 jacmet at uclibc.org
2008-08-16 12:00 jacmet at uclibc.org

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=20080816193637.0E5DF3C7BC@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