是否应该“配置"如果 configure.ac 可用，脚本会被分发吗? [英] Should a "configure" script be distributed if configure.ac is available?

问题描述

目前，我们的安装说明是:

Currently, our installation instructions are:

autoreconf -fi
./configure
...

autoreconf 步骤从 configure.ac 生成 configure 文件，从 生成 Makefile.in 文件Makefile.in.如果其中一个依赖项(比如 pkg-config)没有安装，configure 和 autoreconf 都会失败，尽管后者会打印出一条神秘的错误消息.

The autoreconf step generates the configure file from configure.ac and Makefile.in from Makefile.in. If one of the dependencies (say pkg-config) is not installed, both configure and autoreconf fail although the latter prints a cryptic error message.

发布源码包时，是否应该在包中提供configure 脚本?如果必须分发，还需要包含哪些其他文件?目录 build-aux 和 autom4te.cache 和文件 aclocal.m4 也被创建.

When releasing source tarballs, should the configure script be supplied in the package or not? What other files need to be included if it has to be distributed? The directories build-aux and autom4te.cache and files aclocal.m4 were also created.

推荐答案

在 SCM 存储库中，不应出现任何自动生成的内容(包括配置 - 但此处开发人员的意见离题了).tarball 应包含 autoreconf -fi 和/或 autogen.sh(或您为其选择的任何名称)之后的状态.第三，您也可以使用 make dist，尽管它要求所有应出现在 tarball 中的文件也都列在 Makefile 中.

In an SCM repository, nothing autogenerated should be present (including configure — but developer opinions digress here). A tarball should contain the state after autoreconf -fi and/or autogen.sh (or whichever name you chose for it). Third, you could also use make dist, though it requires that all files that shall appear in the tarball are also listed in the Makefiles.

这篇关于是否应该“配置"如果 configure.ac 可用，脚本会被分发吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！