Go to the first, previous, next, last section, table of contents.
There are a few rules and variables that didn't fit anywhere else.
etagsAutomake will generate rules to generate `TAGS' files for use with GNU Emacs under some circumstances.
If any C, C++ or Fortran 77 source code or headers are present, then
tags and TAGS targets will be generated for the directory.
At the topmost directory of a multi-directory package, a tags
target file will be generated which, when run, will generate a
`TAGS' file that includes by reference all `TAGS' files from
subdirectories.
Also, if the variable ETAGS_ARGS is defined, a tags target
will be generated. This variable is intended for use in directories
which contain taggable source that etags does not understand.
Here is how Automake generates tags for its source, and for nodes in its Texinfo file:
ETAGS_ARGS = automake.in --lang=none \ --regex='/^@node[ \t]+\([^,]+\)/\1/' automake.texi
If you add filenames to `ETAGS_ARGS', you will probably also
want to set `TAGS_DEPENDENCIES'. The contents of this variable
are added directly to the dependencies for the tags target.
Automake will also generate an ID target which will run
mkid on the source. This is only supported on a
directory-by-directory basis.
It is sometimes useful to introduce a new implicit rule to handle a file
type that Automake does not know about. If this is done, you must
notify GNU Make of the new suffixes. This can be done by putting a list
of new suffixes in the SUFFIXES variable.
For instance, currently Automake does not provide any Java support. If you wrote a macro to generate `.class' files from `.java' source files, you would also need to add these suffixes to the list:
SUFFIXES = .java .class
Go to the first, previous, next, last section, table of contents.