autoconf: Writing Autoconf Input

1 
1 3.1 Writing `configure.ac'
1 ==========================
1 
1 To produce a `configure' script for a software package, create a file
1 called `configure.ac' that contains invocations of the Autoconf macros
1 that test the system features your package needs or can use.  Autoconf
11 macros already exist to check for many features; see ⇒Existing
 Tests, for their descriptions.  For most other features, you can use
11 Autoconf template macros to produce custom checks; see ⇒Writing
 Tests, for information about them.  For especially tricky or
1 specialized features, `configure.ac' might need to contain some
11 hand-crafted shell commands; see ⇒Portable Shell Programming
 Portable Shell.  The `autoscan' program can give you a good start in
1 writing `configure.ac' (⇒autoscan Invocation, for more
1 information).
1 
1    Previous versions of Autoconf promoted the name `configure.in',
1 which is somewhat ambiguous (the tool needed to process this file is not
1 described by its extension), and introduces a slight confusion with
1 `config.h.in' and so on (for which `.in' means "to be processed by
1 `configure'").  Using `configure.ac' is now preferred.
1 

Menu

1 
· Shell Script Compiler       Autoconf as solution of a problem
· Autoconf Language           Programming in Autoconf
· Autoconf Input Layout       Standard organization of `configure.ac'
1