Next: , Up: Building documentation   [Index]


8.1 Texinfo

If the current directory contains Texinfo source, you must declare it with the ‘TEXINFOS’ primary. Generally Texinfo files are converted into info, and thus the info_TEXINFOS macro is most commonly used here. Note that any Texinfo source file must end in the ‘.texi’ extension (‘.texinfo’ won’t work).

If the ‘.texi’ file @includes version.texi, then that file will be automatically generated. version.texi defines three Texinfo macros you can reference: EDITION, VERSION, and UPDATED. The first two hold the version number of your package (but are kept separate for clarity); the last is the date the primary file was last modified. The version.texi support requires the mdate-sh program; this program is supplied with Automake.

Sometimes an info file actually depends on more than one ‘.texi’ file. For instance, in the xdvik distribution, kpathsea.texi includes the files install.texi, copying.texi, and freedom.texi. You can tell Automake about these dependencies using the ‘texi_TEXINFOS’ variable. Here is how xdvik could do it:

info_TEXINFOS = kpathsea.texi
kpathsea_TEXINFOS = install.texi copying.texi freedom.texi

Automake will warn if a directory containing Texinfo source does not also contain the file texinfo.tex. This file is supplied with Automake.

Automake generates an install-info target; some people apparently use this.