why is "autoreconf" not used often?

user1783732 picture user1783732 · Oct 9, 2013 · Viewed 9.9k times · Source

I am newbie of Autotools. From my understanding, one would use the following basic steps to build software using Autotools:

  1. autoreconf --install
  2. ./configure
  3. make

However, I noticed that most open source software packages (on Linux) does not need the step 1. They most time just need step 2 and 3 to build. It seems that they already are packaged with Makefile.in. I am wondering why? Do they manually code the Makefile.in, or the software developer uses autoreconf to generate the Makefile.in before creating the software package?

Thanks.

Answer

ldav1s picture ldav1s · Oct 9, 2013

The software developer who creates the tarball (or who checks out the sources from a version control system) will usually invoke autoreconf from a script called bootstrap.sh or autogen.sh which may do other stuff. autoreconf might be invoked by Makefile as well (like when configure.ac has changed).

Most users will never need to run autoreconf, even those who are making some modifications to source (e.g. patches). Only those who need to make modifications to the package itself (making changes to configure.ac and/or Makefile.am) will need autoreconf.