This revision is from 2012/04/15 03:07. You can Restore it.
This is a bit of a confusing process, but here it is in one shot:
- The top-level script (maybe
autogen.sh
) starts -
autoreconf
which runs: -
aclocal
to turnconfigure.ac
intoaclocal.m4
, which is the input for both -
autoconf
, which produces./configure
, and -
autoheader
which makesconfig.h.in
, then -
automake
which turnsMakefile.am
intoMakefile.in
, and then - 5)
./configure
turns the user's input, results of its tests, andMakefile.in
intoMakefile
plusconfig.h.in
intoconfig.h
So the basic pipeline is:
- Developer works on
Makefile.am
andconfigure.ac
- (Some automatic steps)
- Resulting process uses
Makefile
andconfig.h