From f9ba715c8968c506ffb7c6bc5a6d2a64ed273776 Mon Sep 17 00:00:00 2001 From: Alexandre Duret-Lutz Date: Tue, 20 Jan 2004 21:57:41 +0000 Subject: [PATCH] * doc/automake.texi (Dist): Document limitations of distcheck-hook and DISTCHECK_CONFIGURE_FLAGS with regard to subdirs and subpackages. --- ChangeLog | 6 ++++++ doc/automake.texi | 8 ++++++-- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 04035527..32b381eb 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2004-01-20 Ralf Wildenhues (tiny change) + + * doc/automake.texi (Dist): Document limitations of distcheck-hook + and DISTCHECK_CONFIGURE_FLAGS with regard to subdirs and + subpackages. + 2004-01-20 Alexandre Duret-Lutz * doc/automake.texi (Upgrading): New node. diff --git a/doc/automake.texi b/doc/automake.texi index ae2ae558..1f517396 100644 --- a/doc/automake.texi +++ b/doc/automake.texi @@ -5365,13 +5365,17 @@ to supply additional flags to @code{configure}, define them in the @file{Makefile.am}, or on the command line when invoking @code{make}. @vindex DISTCHECK_CONFIGURE_FLAGS -If the @code{distcheck-hook} rule is defined in your +If the @code{distcheck-hook} rule is defined in your top-level @file{Makefile.am}, then it will be invoked by @code{distcheck} after the new distribution has been unpacked, but before the unpacked copy is configured and built. Your @code{distcheck-hook} can do almost anything, though as always caution is advised. Generally this hook is used to check for potential distribution errors not caught by the -standard mechanism. +standard mechanism. Note that @code{distcheck-hook} as well as +@code{DISTCHECK_CONFIGURE_FLAGS} are not honored in a subpackage +@file{Makefile.am}, but the @code{DISTCHECK_CONFIGURE_FLAGS} are +passed down to the @code{configure} script of the subpackage. + Speaking about potential distribution errors, @code{distcheck} will also ensure that the @code{distclean} rule actually removes all built -- 2.43.5