Hello Ralf and all, On Tue, Aug 02, 2005 at 03:30:34PM +0200, Ralf Wildenhues wrote: > | m4_ifset([AC_LIST_HEADERS], > | [CONFIG_H=`echo "AC_LIST_HEADERS" | $SED 's,^[[ ]]*,,;s,[[ > :]].*$,,'`], > | [CONFIG_H=config.h;AC_CONFIG_HEADERS([config.h])]) > | AC_SUBST([CONFIG_H]) > > We compute CONFIG_H, because we later do a > | DEFS = -DHAVE_CONFIG_H="<$(CONFIG_H)>" -DLTDL
OK, so it seems you'd like to know what's the name of the first declared config header. Perhaps the first AC_CONFIG_HEADERS could define a macro, say AH_HEADER which would hold the name. You could then do: m4_ifndef([AH_HEADER], [AC_CONFIG_HEADERS([config.h])]) AC_SUBST([CONFIG_H], ["AH_HEADER"]) Are you willing to write a draft of the documentation? Perhaps a better name than AH_HEADER shall be found, but that'll be part of the discussion about the documentation. What if the first call to AC_CONFIG_HEADERS has a non-literal parameter? AH_HEADER should be consistent with autoheader, but I don't know what autoheader does in such a situation. BTW: > [...] _AC_LIST_TAGS does not contain a list of tags [...] Perhaps I haven't chosen the best name possible. Any suggestions? Looking forward to your help. ;-) Stepan
