* Paul Eggert wrote on Tue, Aug 29, 2006 at 04:34:01PM CEST: > Bruno Haible <bruno@xxxxxxxxx> writes: > > > > Question to the autoconf experts: Is it possible to write a macro > > AM_GETTEXT_NEED_NGETTEXT such that whenever a user writes > > AM_GETTEXT_NEED_NGETTEXT > > AM_GNU_GETTEXT > > or > > AM_GNU_GETTEXT > > AM_GETTEXT_NEED_NGETTEXT > > the AM_GNU_GETTEXT macro "knows" that a AM_GETTEXT_NEED_NGETTEXT invocation > > exists elsewhere? So, a kind of "backward propagation"? > > Nothing comes to me off the top of my head. I suppose the actual work > could be "deferred to the end" but I'm sort of waving my hands here. CVS Libtool has an example usage of the documented Autoconf macro AC_CONFIG_COMMANDS_PRE in libltdl/m4/ltdl.m4:LTDL_INIT. The part in there will be expanded shortly before the config.status generation code. Be warned to not delay more than necessary to this late: in general, users' configure.ac files assume that after your macro invocation, its results are available for further processing, say, in order to fix an intermediate bug of your package in some situation, or to facilitate improvement. (And you would need to adjust your documentation, of course.) If at all possible, it's better to stick to AC_BEFORE or AC_REQUIRE and not use anything else. Another possible, but undocumented way is to divert text to early in the configure script in the manner that (the Autoconf implementation of) AC_CHECK_FUNCS_ONCE does. Don't do this if you expect your macro to work with more than one fixed Autoconf version, and if you do, don't put anything other than simple variable initializations there. Cheers, Ralf, putting up warning signs against future indemnification ;-) _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
