问题描述
我已经在我配置的不同事物中看到了两者.我有什么区别?仅使用一个是否值得注意?或者用哪一个都无所谓?
I have seen both in different things I have configured. What I the difference? Is it notable to use only one? Or does it not matter which one to use?
推荐答案
configure.ac 和 configure.in 是主 Autoconf 源文件的两个可能名称，它们分别是由 autoconf 处理以生成 configure shell 脚本.configure.ac 是新包的首选，configure.in 是一个仍然有效的旧名称.(.in 后缀现在建议只用于将被 config.status 处理的文件，这是运行的 result配置.)
configure.ac and configure.in are two possible names for the master Autoconf source file, which is processed by autoconf to generate the configure shell script. configure.ac is preferred for new packages, configure.in is an older name which still works. (The .in suffix is now recommended to be used only for files which will be processed by config.status, which is the result of running configure.)
Makefile.am 是一个 Automake 源文件.Automake 处理它并生成 Makefile.in，然后由 config.status 进一步处理以生成最终的 Makefile.Automake 生成的 Makefile.in 不能手动编辑.但是，如果一个项目不使用 Automake(但使用 Autoconf)，那么它只会有一个 Makefile.in， 是手工编辑的.
Makefile.am is an Automake source file. Automake processes it and generates Makefile.in, which is then further processed by config.status to generate the final Makefile. An Automake-generated Makefile.in is not meant to be edited by hand. However, if a project doesn't use Automake (but does use Autoconf), then it will only have a Makefile.in which is hand-edited.
有关详细信息，请参阅 http://www.gnu.org/software/autoconf/manual/html_node/Making-configure-Scripts.html - 特别是图表.
For further details see http://www.gnu.org/software/autoconf/manual/html_node/Making-configure-Scripts.html - particularly the diagrams.
这篇关于configure.ac 和 configure.in 和 Makefile.am 和 Makefile.in 之间有什么区别吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！