<!-- This file automatically generated by ParseAutomakeTexinfo utility --> <!-- cvs -d:pserver:anonymous@sources.redhat.com:/cvs/eclipse \ --> <!-- co autotools/ParseTexinfo --> <!DOCTYPE macros [ <!ELEMENT macros (macro)*> <!ELEMENT macro (prototype*,synopsis)> <!ATTLIST macro id ID #REQUIRED > <!ELEMENT synopsis (#PCDATA)*> <!ELEMENT prototype (parameter+)?> <!ELEMENT parameter (#PCDATA)*> <!ATTLIST parameter content CDATA #REQUIRED > ]> <macros> <macro id="AM_CONFIG_HEADER"> <prototype> </prototype> <synopsis> Automake will generate rules to automatically regenerate the config header. This obsolete macro is a synonym of <CODE>AC_CONFIG_HEADERS</CODE> today (Optional). <br><br> </synopsis> </macro> <macro id="AM_ENABLE_MULTILIB"> <prototype> </prototype> <synopsis> This is used when a ``multilib'' library is being built. The first optional argument is the name of the <TT>Makefile</TT> being generated; it defaults to <samp>Makefile</samp>. The second option argument is used to find the top source directory; it defaults to the empty string (generally this should not be used unless you are familiar with the internals). . <br><br> </synopsis> </macro> <macro id="AM_C_PROTOTYPES"> <prototype> </prototype> <synopsis> Check to see if function prototypes are understood by the compiler. If so, define <samp>PROTOTYPES</samp> and set the output variables <samp>U</samp> and <samp>ANSI2KNR</samp> to the empty string. Otherwise, set <samp>U</samp> to <samp>_</samp> and <samp>ANSI2KNR</samp> to <samp>./ansi2knr</samp>. Automake uses these values to implement automatic de-ANSI-fication. <br><br> </synopsis> </macro> <macro id="AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL"> <prototype> </prototype> <synopsis> If the use of <CODE>TIOCGWINSZ</CODE> requires <TT><sys/ioctl.h></TT>, then define <CODE>GWINSZ_IN_SYS_IOCTL</CODE>. Otherwise <CODE>TIOCGWINSZ</CODE> can be found in <TT><termios.h></TT>. This macro is obsolete, you should use Autoconf's <CODE>AC_HEADER_TIOCGWINSZ</CODE> instead. <br><br> </synopsis> </macro> <macro id="AM_INIT_AUTOMAKE"> <prototype> <parameter content="[OPTIONS]"/> </prototype> <prototype> <parameter content="PACKAGE"/> <parameter content="VERSION"/> <parameter content="[NO-DEFINE]"/> </prototype> <synopsis> Runs many macros required for proper operation of the generated Makefiles. <br><br> This macro has two forms, the first of which is preferred. In this form, <CODE>AM_INIT_AUTOMAKE</CODE> is called with a single argument --- a space-separated list of Automake options which should be applied to every <TT>Makefile.am</TT> in the tree. The effect is as if each option were listed in <CODE>AUTOMAKE_OPTIONS</CODE> (Options). <br><br> The second, deprecated, form of <CODE>AM_INIT_AUTOMAKE</CODE> has two required arguments: the package and the version number. This form is obsolete because the <VAR>package</VAR> and <VAR>version</VAR> can be obtained from Autoconf's <CODE>AC_INIT</CODE> macro (which itself has an old and a new form). <br><br> If your <TT>configure.ac</TT> has: <br><br> <TABLE><tr><td>&nbsp;</td><td class=example><pre> AC_INIT(src/foo.c) AM_INIT_AUTOMAKE(mumble, 1.5) </pre></td></tr></table> <br><br> you can modernize it as follows: <br><br> <TABLE><tr><td>&nbsp;</td><td class=example><pre> AC_INIT(mumble, 1.5) AC_CONFIG_SRCDIR(src/foo.c) AM_INIT_AUTOMAKE </pre></td></tr></table> <br><br> Note that if you're upgrading your <TT>configure.ac</TT> from an earlier version of Automake, it is not always correct to simply move the package and version arguments from <CODE>AM_INIT_AUTOMAKE</CODE> directly to <CODE>AC_INIT</CODE>, as in the example above. The first argument to <CODE>AC_INIT</CODE> should be the name of your package (e.g. <samp>GNU Automake</samp>), not the tarball name (e.g. <samp>automake</samp>) that you used to pass to <CODE>AM_INIT_AUTOMAKE</CODE>. Autoconf tries to derive a tarball name from the package name, which should work for most but not all package names. (If it doesn't work for yours, you can use the four-argument form of <CODE>AC_INIT</CODE> --- supported in Autoconf versions greater than 2.52g --- to provide the tarball name explicitly). <br><br> By default this macro <CODE>AC_DEFINE</CODE>'s <samp>PACKAGE</samp> and <samp>VERSION</samp>. This can be avoided by passing the <samp>no-define</samp> option, as in: <TABLE><tr><td>&nbsp;</td><td class=example><pre> AM_INIT_AUTOMAKE([gnits 1.5 no-define dist-bzip2]) </pre></td></tr></table> or by passing a third non-empty argument to the obsolete form. <br><br> </synopsis> </macro> <macro id="AM_PATH_LISPDIR"> <prototype> </prototype> <synopsis> Searches for the program <CODE>emacs</CODE>, and, if found, sets the output variable <CODE>lispdir</CODE> to the full path to Emacs' site-lisp directory. <br><br> Note that this test assumes the <CODE>emacs</CODE> found to be a version that supports Emacs Lisp (such as gnu Emacs or XEmacs). Other emacsen can cause this test to hang (some, like old versions of MicroEmacs, start up in interactive mode, requiring <samp>C-x C-c</samp> to exit, which is hardly obvious for a non-emacs user). In most cases, however, you should be able to use <samp>C-c</samp> to kill the test. In order to avoid problems, you can set <CODE>EMACS</CODE> to ``no'' in the environment, or use the <samp>--with-lispdir</samp> option to <CODE>configure</CODE> to explicitly set the correct path (if you're sure you have an <CODE>emacs</CODE> that supports Emacs Lisp. <br><br> </synopsis> </macro> <macro id="AM_PROG_AS"> <prototype> </prototype> <synopsis> Use this macro when you have assembly code in your project. This will choose the assembler for you (by default the C compiler) and set <CODE>CCAS</CODE>, and will also set <CODE>CCASFLAGS</CODE> if required. <br><br> </synopsis> </macro> <macro id="AM_PROG_CC_C_O"> <prototype> </prototype> <synopsis> This is like <CODE>AC_PROG_CC_C_O</CODE>, but it generates its results in the manner required by automake. You must use this instead of <CODE>AC_PROG_CC_C_O</CODE> when you need this functionality. <br><br> </synopsis> </macro> <macro id="AM_PROG_LEX"> <prototype> </prototype> <synopsis> Like <CODE>AC_PROG_LEX</CODE> (@pxref{Particular Programs, , Particular Program Checks, autoconf, The Autoconf Manual}), but uses the <CODE>missing</CODE> script on systems that do not have <CODE>lex</CODE>. <samp>HP-UX 10</samp> is one such system. <br><br> </synopsis> </macro> <macro id="AM_PROG_GCJ"> <prototype> </prototype> <synopsis> This macro finds the <CODE>gcj</CODE> program or causes an error. It sets <samp>GCJ</samp> and <samp>GCJFLAGS</samp>. <CODE>gcj</CODE> is the Java front-end to the GNU Compiler Collection. <br><br> </synopsis> </macro> <macro id="AM_SYS_POSIX_TERMIOS"> <prototype> </prototype> <synopsis> Check to see if POSIX termios headers and functions are available on the system. If so, set the shell variable <CODE>am_cv_sys_posix_termios</CODE> to <samp>yes</samp>. If not, set the variable to <samp>no</samp>. This macro is obsolete, you should use Autoconf's <CODE>AC_SYS_POSIX_TERMIOS</CODE> instead. <br><br> </synopsis> </macro> <macro id="AM_WITH_DMALLOC"> <prototype> </prototype> <synopsis> Add support for the <A HREF="ftp://ftp.letters.com/src/dmalloc/dmalloc.tar.gz>dmalloc</A> package. If the user configures with <samp>--with-dmalloc</samp>, then define <CODE>WITH_DMALLOC</CODE> and add <samp>-ldmalloc</samp> to <CODE>LIBS</CODE>. <br><br> </synopsis> </macro> <macro id="AM_WITH_REGEX"> <prototype> </prototype> <synopsis> Adds <samp>--with-regex</samp> to the <CODE>configure</CODE> command line. If specified (the default), then the <samp>regex</samp> regular expression library is used, <TT>regex.o</TT> is put into <samp>LIBOBJS</samp>, and <samp>WITH_REGEX</samp> is defined. If <samp>--without-regex</samp> is given, then the <samp>rx</samp> regular expression library is used, and <TT>rx.o</TT> is put into <samp>LIBOBJS</samp>. <br><br> </DL> <br><br> @node Private macros </synopsis> </macro> </macros>