blocks|key|3284386|text|Makefile语法很微妙，很容易激怒。我可能会建议你看看documentation+for+make，特别是关于suffix+rules的部分。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3284387|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/make/manual/|1|http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html^0|0|8|T|M|0|1L|C|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]|$9|V|A|W|1|X]]|E|$]]|$1|F|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]]]

The <code>Makefile</code> syntax is subtle and quick to anger. I might suggest having a look at the <a href="http://www.gnu.org/software/make/manual/" rel="nofollow noreferrer">documentation for make</a>, particularly the part about <a href="http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html" rel="nofollow noreferrer">suffix rules</a>.

blocks|key|323924|text|第一行Fortran清除了所有关于“内置”后缀的知识；第二行恢复了后缀.f+(传统的.SUFFIXES+)和.o+(对象文件)。当不能使用其他规则时，将使用.DEFAULT规则。最后一条规则使用$(FC)编译器将.f文件编译成.o文件。@的意思是不要回显命令，这让我很恼火(我更喜欢看到用来进行编译的命令)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|323925|我在makefile解压缩中看不到*.suffixes，所以我不能告诉你它是什么意思。|323926|entityMap^0|Z|2|16|9|1I|2|26|8|2P|5|2Y|2|35|2|3A|1|0|H|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|I|$]]

The first <code>.SUFFIXES</code> line cleans out all knowledge of 'built-in' suffixes; the second reinstates the suffixes <code>.f</code> (traditionally Fortran) and <code>.o</code> (object files). The <code>.DEFAULT</code> rule is used when nothing else can be used. And the last rule compiles a <code>.f</code> file into a <code>.o</code> file using the <code>$(FC)</code> compiler. The <code>@</code> means don't echo the command - and annoys me (I prefer to see the commands used to do the compilation).

I can't see a <code>*.suffixes</code> in the makefile extracts, so I can't tell you what it means.

blocks|key|3284432|text|你问题的第一行只是一个标准的Makefile规则。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3284433|vpath.o:+make.h+config.h+getopt.h+gettext.h+dep.h|code-block|syntax|javascript|3284434|.o文件是一个目标文件；它是源文件和最终编译的二进制文件之间的中间产品。它包含已编译的代码，但尚未链接到一个完整的库或二进制文件中。这条规则只说明vpath.o依赖于make.h、config.h等，每次更改时，都应该重新编译。构建vpath.o所需的命令应紧跟在后续行之后，并以制表符缩进。(如果我重复了您已经知道的内容，很抱歉；我不确定您对第一行中的哪部分感到困惑)。|offset|length|style|CODE|3284435|.SUFFIXES并不是指实际的文件后缀；它只是makefile中的一种特殊规则，用于配置“后缀规则”。|3284436|后缀规则是.a.b形式的规则，就像您在.f.o规则中看到的那样。它们是一种告诉make的方式，只要您看到.f文件(源文件)，就可以遵循该规则从该文件生成.o文件(目标文件)，其中$<表示源文件，$@表示目标文件。|3284437|.SUFFIXES“目标”是一种定义可以在后缀规则中使用的后缀的方法。在没有先决条件的情况下使用时，它会清除内置的后缀列表；当与先决条件一起使用时，它会将这些后缀添加到它的已知后缀列表中，这些后缀可能会在后缀规则中使用。|3284438|在GNU+make中，您可以使用更强大、更清晰的%25来形成模式规则，例如：|3284439|%25.o:+%25.c
++++gcc+-c+-o+$@+$<|3284440|这相当于后缀规则：|3284441|.c.o:
++++gcc+-c+-o+$@+$<|3284442|有关更多信息，请参阅GNU+Make+documentation+(但其中也提到了GNU扩展)，或者参阅Single+Unix+Specification/POSIX了解通用的、可移植的语法。|3284443|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html|1|http://www.opengroup.org/onlinepubs/009695399/utilities/make.html^0|0|0|0|2|21|7|2B|6|2I|8|38|7|0|0|9|0|5|4|J|4|13|4|1G|2|24|2|2H|2|2P|2|0|0|9|0|5|4|O|1|0|0|0|0|A|M|0|1G|V|1|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1E|8|@$I|1F|J|1G|K|L]|$I|1H|J|1I|K|L]|$I|1J|J|1K|K|L]|$I|1L|J|1M|K|L]|$I|1N|J|1O|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1P|8|@$I|1Q|J|1R|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1S|8|@$I|1T|J|1U|K|L]|$I|1V|J|1W|K|L]|$I|1X|J|1Y|K|L]|$I|1Z|J|20|K|L]|$I|21|J|22|K|L]|$I|23|J|24|K|L]|$I|25|J|26|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|27|8|@$I|28|J|29|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|2A|8|@$I|2B|J|2C|K|L]|$I|2D|J|2E|K|L]]|9|@]|A|$]]|$1|U|3|V|5|D|7|2F|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|2G|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|2H|8|@]|9|@]|A|$E|F]]|$1|10|3|11|5|6|7|2I|8|@]|9|@$I|2J|J|2K|1|2L]|$I|2M|J|2N|1|2O]]|A|$]]|$1|12|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]]]

The first line in your question is just a standard Makefile rule.

<pre><code>vpath.o: make.h config.h getopt.h gettext.h dep.h
</code></pre>

A <code>.o</code> file is an object file; it's an intermediate product in between your source files and the final compiled binary. It contains compiled code, but it hasn't been linked together into a complete library or binary yet. This rule just says that <code>vpath.o</code> depends on <code>make.h</code>, <code>config.h</code>, etc., and each time those are changed, it should be re-compiled. The commands necessary to build <code>vpath.o</code> should follow on subsequent lines, indented with a tab character. (Apologies if I'm repeating stuff you already know; I wasn't sure what part of that first line you were confused about).

The <code>.SUFFIXES</code> doesn't refer to an actual file suffix; it's just a special kind of rule in a makefile which is used for configure "suffix rules".

Suffix rules are rules of the form <code>.a.b</code>, such as you see with your <code>.f.o</code> rule. They are a way of telling <code>make</code> that any time you see, say, a <code>.f</code> file (the source file), you can make a <code>.o</code> file (the target file) from it by following that rule, where <code>$&lt;</code> indicates the source file and <code>$@</code> represents the target file.

the <code>.SUFFIXES</code> "target" is a way to define which suffixes you can use in your suffix rules. When used with no prerequisites, it clears the built in list of suffixes; when used with prerequisites, it adds those to its list of known suffixes that may be used in suffix rules.

In GNU <code>make</code>, you can use the more powerful and more clear <code>%</code> to form pattern rules, like:

<pre><code>%.o: %.c
 gcc -c -o $@ $&lt;
</code></pre>

which is the equivalent of the suffix rule:

<pre><code>.c.o:
 gcc -c -o $@ $&lt;
</code></pre>

See the <a href="http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html" rel="noreferrer">GNU Make documentation</a> for more information (but which also mentions GNU extensions), or the <a href="http://www.opengroup.org/onlinepubs/009695399/utilities/make.html" rel="noreferrer">Single Unix Specification/POSIX</a> for the common, portable syntax.

blocks|key|3071217|text|如前所述，这行代码|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3071218|.SUFFIXES：|3071219|会删除所有已知的后缀。这样做的目的是为了：|3071220|3071221|默认后缀不会干扰您的特殊后缀。|unordered-list-item|3071222|不同的make程序具有不兼容的后缀列表和隐式规则，这有时会在General+Conventions+for+Makefiles+|offset|length|3071223|中造成混淆或不当行为。|3071224|如果您正在使用GNU，最好使用模式规则而不是后缀规则，因为它们(后缀规则)是为了兼容性而存在的，reasons.Also后缀规则不能有自己的先决条件。|3071225|因此，您将重写表单的后缀规则：|3071226|.f.o：|3071227|..。|3071228|作为表单的模式规则：|3071229|%25.o:%25.f：|3071230|3071231|请注意，在后缀规则中，先决条件前缀排在第一位，目标后缀排在第二位，而对于模式规则，则是相反的(并且不那么容易混淆)。|3071232|如果您计划更多地使用makefile，也可以查看在线提供的Managing+Projects+with+GNU+Make一书。|3071233|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/prep/standards/html_node/Makefile-Basics.html|1|http://oreilly.com/catalog/make3/book/index.csp^0|0|0|0|0|0|U|X|0|0|0|0|0|0|0|0|0|0|0|T|V|1|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1K|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|1L|8|@]|9|@$L|1M|M|1N|1|1O]]|A|$]]|$1|N|3|O|5|6|7|1P|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1R|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1S|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1T|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1V|8|@]|9|@]|A|$]]|$1|11|3|W|5|6|7|1W|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1X|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1Y|8|@]|9|@$L|1Z|M|20|1|21]]|A|$]]|$1|16|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|17|$18|$5|19|1A|1B|A|$1C|1D]]|1E|$5|19|1A|1B|A|$1C|1F]]]]

As already mentioned the line 
.SUFFIXES: 
would delete all the known suffixes. This is done so that the:

<ul>
<li> default suffixes wouldn't interfere with your special suffixes. 
<li> Different make programs have incompatible suffix lists and implicit rules, 
 and this sometimes creates confusion or misbehavior 
 <a href="http://www.gnu.org/prep/standards/html_node/Makefile-Basics.html" rel="nofollow noreferrer">General Conventions for Makefiles</a>
</ul>

If you are using GNU make it is better to use pattern rules instead of suffix rules
as they (suffix rules) exist for compatiblity reasons.Also suffix rules cannot have
prerequisites of their own.

So you would rewrite the suffix rule of form:

.f.o: 
...

as a pattern rule of the form:

%.o:%.f: 
...

Note that in suffix rules prerequisite prefix comes first and the target suffix comes second, where as with pattern rules it is the other way round (and less confusing).

If you plan to work more with makefiles, also check the book
<a href="http://oreilly.com/catalog/make3/book/index.csp" rel="nofollow noreferrer">Managing Projects with GNU Make</a>
which is available online.

blocks|key|3284542|text|您还可以使用后缀规则链，如下面的规则所示，从gnuplot文件生成tex然后pdf：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3284543|.SUFFIXES:+.plt+.tex+.pdf

#+(notice+that+there+should+be+tabs+prefixing+the+lines+after+the+rule)
%25.tex:+%25.plt
gnuplot+-e+"+\
set+format+'$$%25g$$'+;+\
set+terminal+epslatex+standalone+color+;+\
set+output+'$@'+\
"+$<

%25.pdf:+%25.tex
pdflatex+$<

all:+test.pdf|code-block|syntax|javascript|3284544|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

you can also use chain of the suffix rule, such as in the following one to generate tex then pdf from a gnuplot file:

<pre><code>.SUFFIXES: .plt .tex .pdf

# (notice that there should be tabs prefixing the lines after the rule)
%.tex: %.plt
gnuplot -e " \
set format '$$%g$$' ; \
set terminal epslatex standalone color ; \
set output '$@' \
" $&lt;

%.pdf: %.tex
pdflatex $&lt;

all: test.pdf
</code></pre>

I have seen commands like this all over Makefiles, which I don't quite understand:

<pre><code>vpath.o: make.h config.h getopt.h gettext.h dep.h
</code></pre>

and

<pre><code>.SUFFIXES:
.SUFFIXES: .f .o
#
# %------------------%
# | Default command. |
# %------------------%
#
.DEFAULT:
 @$(ECHO) "Unknown target $@, try: make help"
#
# %-------------------------------------------%
# | Command to build .o files from .f files. |
# %-------------------------------------------%
#
.f.o:
 @$(ECHO) Making $@ from $&lt;
 @$(FC) -c $(FFLAGS) $&lt;
</code></pre>

What does the <code>*.o</code> and <code>*.suffixes</code> mean?

Note: The two commands are from different parts of the script.

What does *.o/.suffixes in makefile mean?

我在Makefiles中看到过类似这样的命令，但我不太理解：vpath.o: make.h config.h getopt.h gettext.h dep.h和.SUFFIXES:.SUFFIXES:  .f  .o## %------------------%# | Default command. |# %----...

问makefile中的*.o/.后缀是什么意思？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问makefile中的*.o/.后缀是什么意思？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问makefile中的*.o/.后缀是什么意思？
EN