configure.ac和configure.in以及Makefile.am和Makefile.in之间有什么区别? [英] Any difference between configure.ac and configure.in, and Makefile.am and Makefile.in?

问题描述

我已经在配置的不同事物中看到了两者.我有什么区别?仅使用一个值得注意吗?还是使用哪一个都没关系?

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处理的文件，这是运行configure的结果.)

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之间有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！