为什么是"autoreconf"?不经常使用? [英] why is "autoreconf" not used often?

问题描述

我是Autotools的新手.据我了解，人们将使用以下基本步骤来使用Autotools构建软件:

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

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

但是，我注意到大多数开放源代码软件包(在Linux上)不需要步骤1.大多数时候，它们仅需要步骤2和3即可构建.似乎它们已经与Makefile.in打包在一起了.我想知道为什么吗?他们是手动编写Makefile.in的代码，还是在创建软件包之前软件开发人员使用autoreconf生成Makefile.in?

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?

谢谢.

推荐答案

创建压缩包(或从版本控制系统中检出源代码)的软件开发人员通常会从名为bootstrap.sh的脚本中调用autoreconf.或autogen.sh可能会做其他事情. autoreconf也可能由Makefile调用(例如configure.ac更改时).

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).

大多数用户甚至永远不需要运行autoreconf，即使是那些对源代码进行了某些修改(例如补丁程序)的用户.只有那些需要对程序包本身进行修改(对configure.ac和/或Makefile.am进行更改)的人才需要autoreconf.

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.

这篇关于为什么是"autoreconf"?不经常使用?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！