APCUPSD site configuration relies, for its multi-platform design,
on GNU's autoconf. This is not only an option: it is mandatory because
of the number of things that needs to be checked before actually start
the compilation.
Therefore it is paramount for a developer, especially for a distribution mantainer, to know at least the basics of autoconf.
If you need to check for a new function or put a new target in Makefile, you have to modify configure.in or Makefile.in.
The $(allexe) variable of the Makefile.in contain all the files that
will be compiled in that directory. If you add a new file into the sources,
add it to the Makefile.in, then you have just to run ./configure to update
the Makefile(s) and `config.h'. Be warned. After modifying configure.in,
Makefile.in, aclocal.m4 or acconfig.h the best thing you can do is:
A script called scripts/autoregen.sh automate these steps. Autoregen.sh
understand the flags "config" and "compile". Without flags it will regenerate
everything, compile and distclean the source tree.