2004-10-12 Alexandre Duret-Lutz <adl@gnu.org>
+ * 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.
+
* configure.ac: Export @am_AUTOCONF@.
* tests/defs.in (AUTOCONF): Define as @am_AUTOCONF@, not @AUTOCONF@,
so the test suite runs `autoconf' and not `missing --run autoconf'.
@samp{install-exec}.
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
@samp{install-data}.
@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
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
+@code{barexec_SCRIPTS} 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