没有Makefile.am Makefile.in文件的项目 [英] Makefile.in without Makefile.am in projects

问题描述

在几个项目我见过没有Makefile.am的Makefile.in。例如。庆典 http://git.savannah.gnu.org/cgit/bash.git /树/ 并dtach http://dtach.cvs.sourceforge.net / viewvc / dtach / dtach /

In several projects I have seen the Makefile.in without Makefile.am . E.g. bash http://git.savannah.gnu.org/cgit/bash.git/tree/ and dtach http://dtach.cvs.sourceforge.net/viewvc/dtach/dtach/

我一直以为是Makefile.in由automake产生的。另外随着Makefile.am是一个用户编写的文件，我不会想到它会从code库被省略。在bash的源代码树中，Makefile.in是远远太大而手写和Makefile.in在dtach看起来也产生。如何在项目中生成的Makefile.in喜欢这两个？

I always thought that Makefile.in was generated by automake. Also with Makefile.am being a user written file I would not have thought it would be omitted from the code repository. In the bash source tree, the Makefile.in is far too big to be hand written and the Makefile.in in dtach also looks generated. How was the Makefile.in generated in projects like these two?

推荐答案

的的libtool 和的automake 自动工具可这取决于你所需要的的autoconf 做使用彼此独立（或根本没有）。因此，它不是的需要的使用的automake 生成 Makefile.in 。

The libtool and automake autotools can be used independently of one another (or not at all), depending on what you need autoconf to do. Therefore, it's not required to use automake to generate Makefile.in.

的的automake 工具还明显输出，它已被用于：

The automake tool also conspicuously outputs that it has been used:

＃Makefile.in。

# Makefile.in generated by automake 1.11.1 from Makefile.am.

所以，这可能是 Makefile.in 是你所看到的手动的编辑。

So it's likely that the Makefile.ins you have seen are edited "by hand".

这篇关于没有Makefile.am Makefile.in文件的项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！