From: Richard M. Stallman <rms@gnu.org>
Date: Tue, 27 Feb 1996 07:36:22 +0000 (+0000)
Subject: Replace `strip' target with `install-strip'.
X-Git-Tag: fsf-origin~187
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c0dd463557d033a20df2b5d30ef787c1ef8d9d10;p=thirdparty%2Fautoconf.git

Replace `strip' target with `install-strip'.
---

diff --git a/doc/make-stds.texi b/doc/make-stds.texi
index 1a5c03fb..159cad3d 100644
--- a/doc/make-stds.texi
+++ b/doc/make-stds.texi
@@ -495,7 +495,7 @@ simple test to verify that a program is properly installed, this target
 should run that test.
 
 Do not strip executables when installing them.  Devil-may-care users can
-use the @code{strip} target to do that.
+use the @code{install-strip} target to do that.
 
 If possible, write the @code{install} target rule so that it does not
 modify anything in the directory where the program was built, provided
@@ -547,11 +547,14 @@ create).
 This rule should not modify the directories where compilation is done,
 only the directories where files are installed.
 
-@item strip
-Strip the installed executable files---that is to say, the copies made
-in the installation directories by the @code{install} target.  This
-target should not alter the executable files in the directory where the
-program was built.
+@item install-strip
+Like @code{install}, but strip the executable files while installing
+them.  The definition of this target can be very simple:
+
+@example
+install-strip:
+        $(MAKE) INSTALL_PROGRAM='$(INSTALL_PROGRAM) -s' install
+@end example
 
 Normally we do not recommend stripping an executable unless you are sure
 the program has no bugs.  However, it can be reasonable to install a
diff --git a/make-stds.texi b/make-stds.texi
index 1a5c03fb..159cad3d 100644
--- a/make-stds.texi
+++ b/make-stds.texi
@@ -495,7 +495,7 @@ simple test to verify that a program is properly installed, this target
 should run that test.
 
 Do not strip executables when installing them.  Devil-may-care users can
-use the @code{strip} target to do that.
+use the @code{install-strip} target to do that.
 
 If possible, write the @code{install} target rule so that it does not
 modify anything in the directory where the program was built, provided
@@ -547,11 +547,14 @@ create).
 This rule should not modify the directories where compilation is done,
 only the directories where files are installed.
 
-@item strip
-Strip the installed executable files---that is to say, the copies made
-in the installation directories by the @code{install} target.  This
-target should not alter the executable files in the directory where the
-program was built.
+@item install-strip
+Like @code{install}, but strip the executable files while installing
+them.  The definition of this target can be very simple:
+
+@example
+install-strip:
+        $(MAKE) INSTALL_PROGRAM='$(INSTALL_PROGRAM) -s' install
+@end example
 
 Normally we do not recommend stripping an executable unless you are sure
 the program has no bugs.  However, it can be reasonable to install a