[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FYI: more install-exec-hook/install-data-hook cross-references

From: Alexandre Duret-Lutz
Subject: FYI: more install-exec-hook/install-data-hook cross-references
Date: Tue, 12 Oct 2004 21:55:45 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

I'm checking this in on HEAD and branch-1-9.  It was prompted by
a mistaken bug report.

2004-10-12  Alexandre Duret-Lutz  <address@hidden>

        * doc/automake.texi (Install): Link to node Extending for examples.
        (Extending): More comments about install-data-hook vs
        install-exec-hook, and link to Install.

Index: doc/automake.texi
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision
diff -u -r1.44.2.12 automake.texi
--- doc/automake.texi   11 Oct 2004 18:48:19 -0000
+++ doc/automake.texi   12 Oct 2004 19:53:05 -0000
@@ -5441,7 +5441,7 @@
 Any variable using a user-defined directory prefix with @samp{exec} in
-the name (e.g. @samp{myexecbin_PROGRAMS} is installed by
+the name (e.g. @samp{myexecbin_PROGRAMS}) is installed by
 @samp{install-exec}.  All other user-defined prefixes are installed by
@@ -5458,7 +5458,7 @@
 @code{install-data-hook}.  These hooks are run after all other install
 rules of the appropriate type, exec or data, have completed.  So, for
 instance, it is possible to perform post-installation modifications
-using an install hook.
+using an install hook.  @ref{Extending} gives some examples.
 @cindex Install hook
 @section Staged installs
@@ -6823,6 +6823,13 @@
 symbolic link, not the real binary.  Also we @code{cd} into the
 destination directory in order to create relative links.
+When writing @code{install-exec-hook} or @code{install-data-hook},
+please bear in mind that the exec/data distinction is based on the
+installation directory, not on the primary used (@pxref{Install}).  So
+a @code{foo_SCRIPTS} will be installed by @code{install-data}, and a
address@hidden will be installed by @code{install-exec}.  You
+should define your hooks consequently.
 @c FIXME should include discussion of variables you can use in these
 @c rules
Alexandre Duret-Lutz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]