In general, this is what you need to do to use GNU Autoconf in a program:

1. run `autoscan' in the base directory of your project.  This will create
a `configure.scan' file, which is really a `configure.in' file.

2. take a look at `configure.scan' and make sure everything looks ok.

3. rename `configure.scan' to `configure.in'

4. rename all your `Makefile' files to `Makefile.in'

5. Now edit all your `Makefile.in' files, and be sure you replace all
macros with the following:

  bindir: where binaries will be installed
  datadir: where data will be installed
  includedir: where `.h' files will be installed
  infodir: where info files will be installed
  libdir: where libs will be installed
  mandir: top level where to install man files
  prefix: installation prefix

  CC: the C compiler
  CFLAGS: flags for CC
  CPPFLAGS: `-I' flags for the compiler (preprocessor)
  DEFS: `-D' flags for the compiler
  LDFLAGS: flags for the linker
  LIBS: `-L' and `-l' flags for the linker

Actually, you need to use "@CC@" macros.  For example:

  CC=@CC@
  DEFS=-Dmydefs @DEFS@


6. run `autoconf' to generate the `configure' script


** NOTE TO SELF: THERE IS NO POINT IN CHECKING THE `configure' SCRIPT
   INTO VERSION CONTROL, SINCE THIS IS PURELY A GENERATED FILE, AND
   DEPENDS ONLY ON THE `configure.in' FILE.


As a user, to build your project, just do this:

1. run `configure'

2. type `make'


For GNU Robots, I just needed to modify the base Makefile (Makefile.in).
The subdir Makefiles were just renamed as Makefile.  Actually, I also added
a command for `make distclean' that removed the (generated) Makefile files.
