blocks|key|184228|text|试试这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184229|SUBDIRS+=+foo+bar+baz

subdirs:
++++for+dir+in+$(SUBDIRS);+do+\
++++++++$(MAKE)+-C+$$dir;+\
++++done|code-block|syntax|javascript|184230|这可能会帮助你link|offset|length|184231|编辑:还可以执行以下操作：|184232|最简单的方法是这样做：|184233|CODE_DIR+=+code

.PHONY:+project_code

project_code:
+++++++$(MAKE)+-C+$(CODE_DIR)|184234|.PHONY规则意味着project_code不是需要构建的文件，而-C标志表示目录中的更改(相当于在调用make之前运行cd代码)。您可以使用相同的方法调用代码Makefile中的其他目标。|184235|例如：|184236|clean:
+++$(MAKE)+-C+$(CODE_DIR)+clean|184237|Source|184238|entityMap|0|LINK|mutability|MUTABLE|url|http://lackof.org/taggart/hacking/make-example/|1|https://stackoverflow.com/questions/3494999/subdirectories-and-makefiles^0|0|0|7|4|0|0|0|0|0|0|0|0|0|6|1|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1A|8|@]|9|@$I|1B|J|1C|1|1D]]|A|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1K|8|@]|9|@$I|1L|J|1M|1|1N]]|A|$]]|$1|Y|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]]]

Try this :

<pre><code>SUBDIRS = foo bar baz

subdirs:
 for dir in $(SUBDIRS); do \
 $(MAKE) -C $$dir; \
 done
</code></pre>

This may help you <a href="http://lackof.org/taggart/hacking/make-example/" rel="noreferrer">link</a>

Edit : you can also do : 

The simplest way is to do:

<pre><code>CODE_DIR = code

.PHONY: project_code

project_code:
 $(MAKE) -C $(CODE_DIR)
</code></pre>

The .PHONY rule means that project_code is not a file that needs to be
built, and the -C flag indicates a change in directory (equivalent to
running cd code before calling make). You can use the same approach
for calling other targets in the code Makefile.

For example:

<pre><code>clean:
 $(MAKE) -C $(CODE_DIR) clean
</code></pre>

<a href="https://stackoverflow.com/questions/3494999/subdirectories-and-makefiles">Source</a>

blocks|key|184242|text|在单个配方中的for循环中执行子make存在各种问题。执行多个子目录的最佳方法如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184243|SUBDIRS+:=+$(wildcard+*/.)

all:+$(SUBDIRS)
$(SUBDIRS):
++++++++$(MAKE)+-C+$@

.PHONY:+all+$(SUBDIRS)|code-block|syntax|javascript|184244|(只是为了指出这是GNU+make的具体版本；您没有提到对您正在使用的make版本的任何限制)。|184245|ETA这是一个支持多个顶级目标的版本。|184246|TOPTARGETS+:=+all+clean

SUBDIRS+:=+$(wildcard+*/.)

$(TOPTARGETS):+$(SUBDIRS)
$(SUBDIRS):
++++++++$(MAKE)+-C+$@+$(MAKECMDGOALS)

.PHONY:+$(TOPTARGETS)+$(SUBDIRS)|184247|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

There are various problems with doing the sub-make inside a for loop in a single recipe. The best way to do multiple subdirectories is like this:

<pre><code>SUBDIRS := $(wildcard */.)

all: $(SUBDIRS)
$(SUBDIRS):
 $(MAKE) -C $@

.PHONY: all $(SUBDIRS)
</code></pre>

(Just to point out this is GNU make specific; you didn't mention any restrictions on the version of make you're using).

ETA Here's a version which supports multiple top-level targets.

<pre><code>TOPTARGETS := all clean

SUBDIRS := $(wildcard */.)

$(TOPTARGETS): $(SUBDIRS)
$(SUBDIRS):
 $(MAKE) -C $@ $(MAKECMDGOALS)

.PHONY: $(TOPTARGETS) $(SUBDIRS)
</code></pre>

blocks|key|2794703|text|GNU+make有一个名为prorab的库，它支持在子目录中包含独立的makefile。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2794704|有关github的一些信息：https://github.com/cppfw/prorab/blob/master/wiki/HomePage.adoc|2794705|基本上，使用prorab调用子目录中的所有makefile如下所示：|2794706|include+prorab.mk

$(eval+$(prorab-build-subdirs))|code-block|syntax|javascript|2794707|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/cppfw/prorab/blob/master/wiki/HomePage.adoc^0|D|6|0|E|1Q|0|0|6|6|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|H|3|I|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|16|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

There is a library called prorab for GNU make which supports inclusion of standalone makefiles in subdirectories.
Some info on github: <a href="https://github.com/cppfw/prorab/blob/master/wiki/HomePage.adoc" rel="nofollow noreferrer">https://github.com/cppfw/prorab/blob/master/wiki/HomePage.adoc</a>
Basically, with prorab invoking all makefiles in subdirectories looks like this:
<pre><code>include prorab.mk

$(eval $(prorab-build-subdirs))
</code></pre>

blocks|key|184280|text|由于我不知道MAKECMDGOALS变量，并且忽略了MadScientist有自己的多个顶级目标的实现，所以我编写了一个替代实现。也许有人会发现它很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184281|SUBDIRS+:=+$(wildcard+*/.)

define+submake
++++++++for+d+in+$(SUBDIRS);++++++++++++++++++\
++++++++do++++++++++++++++++++++++++++++++++++\
++++++++++++++++$(MAKE)+$(1)+--directory=$$d;+\
++++++++done
endef

all:
++++++++$(call+submake,$@)

install:
++++++++$(call+submake,$@)

.PHONY:+all+install+$(SUBDIRS)|code-block|syntax|javascript|184282|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|$]]

Since I was not aware of the MAKECMDGOALS variable and overlooked that MadScientist has its own implementation of multiple top-level targets, I wrote an alternative implementation. Maybe someone find it useful.

<pre><code>SUBDIRS := $(wildcard */.)

define submake
 for d in $(SUBDIRS); \
 do \
 $(MAKE) $(1) --directory=$$d; \
 done
endef

all:
 $(call submake,$@)

install:
 $(call submake,$@)

.PHONY: all install $(SUBDIRS)
</code></pre>

blocks|key|3007419|text|为了使子目录中的所有单独目标都可以从顶层获得(您将需要定义SUBDIRS变量才能使用以下代码片段-您可以使用MadScientist的答案)，在MadScientist的答案之后只需加一点糖霜：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3007420|#+Make+all+the+individual+targets+in+the+sub-directories+available+from+the+top
#+level;+as+in,+for+instance,+`make+foo/my_program`+or+`make+bar/clean`
$(foreach+__dir__,$(SUBDIRS),$(__dir__)/%25):
++++++++@$(MAKE)+-C+'$(@D)'+'$(@F)'|code-block|syntax|javascript|3007421|3007422|使用上面的代码，您可以运行，例如，|3007423|make+foo/my_program|3007424|或|3007425|make+bar/clean|3007426|此外，通过粘贴上面的代码，您甚至可以使用子目录中的单个目标作为顶级目标的先决条件。例如：|3007427|my_target:+my_subdirectory/my_prerequisite
++++++++'my_subdirectory/my_prerequisite'+>+'my_target'|3007428|…对于上面的示例，从顶层启动make+my_target将首先构建my_subdirectory/my_prerequisite程序，然后运行后者来构建my_target文件。|3007429|entityMap^0|T|7|0|0|0|0|0|0|0|0|0|E|E|X|V|24|9|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|16|8|@]|D|@]|E|$]]|$1|N|3|O|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|P|3|Q|5|6|7|18|8|@]|D|@]|E|$]]|$1|R|3|S|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|T|3|U|5|6|7|1A|8|@]|D|@]|E|$]]|$1|V|3|W|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|X|3|Y|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|10|$]]

Only a small icing on the cake after MadScientist's answer in order to make all the individual targets in the sub-directories available from the top level (you will need to have the <code>SUBDIRS</code> variable defined in order to use the following snippet – you can use MadScientist's answer for that):

<pre><code># Make all the individual targets in the sub-directories available from the top
# level; as in, for instance, `make foo/my_program` or `make bar/clean`
$(foreach __dir__,$(SUBDIRS),$(__dir__)/%):
 @$(MAKE) -C '$(@D)' '$(@F)'
</code></pre>

<hr>

With the code above you can run, for instance,

<pre><code>make foo/my_program
</code></pre>

or

<pre><code>make bar/clean
</code></pre>

Furthermore, by pasting the code above you can even use an individual target from a sub-directory as a prerequisite for a target in the top level. For example:

<pre><code>my_target: my_subdirectory/my_prerequisite
 'my_subdirectory/my_prerequisite' &gt; 'my_target'
</code></pre>

…With the example above, launching <code>make my_target</code> from the top level will first build the <code>my_subdirectory/my_prerequisite</code> program, then the latter will be run for building the <code>my_target</code> file.

blocks|key|3007461|text|这是MadScientist's+answer的另一种方法。GNU是一个特定于.PHONY的特性，可用于强制make递归到每个子目录中。但是，make的一些非GNU版本不支持.PHONY，因此另一种选择是force+target。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3007462|没有处方或先决条件的|3007463|+4.7规则|blockquote|3007464|3007465|如果一个规则没有先决条件或配方，并且该规则的目标是一个不存在的文件，那么make会认为只要运行它的规则，这个目标就会被更新。这意味着依赖于此的所有目标都将始终运行它们的配方。|3007466|下面举一个例子来说明这一点：|3007467|清理:强制rm+$(对象)强制：|3007468|在这里，目标‘FORCE’满足特殊条件，因此依赖于它的目标clean被强制运行其配方。“FORCE”这个名字没有什么特别之处，但这是一个常用的名字。|3007469|如你所见，以这种方式使用‘FORCE’与使用‘.PHONY:clean’具有相同的结果。|3007470|使用‘.PHONY’更明确，效率更高。然而，make的其他版本不支持‘.PHONY’；因此，‘FORCE’出现在许多makefile中。请参阅假目标。|3007471|3007472|下面是一个最小的示例，它将make递归到每个子目录中，每个子目录可能包含一个Makefile。如果您只是运行make，那么只会处理第一个子目录，它是不确定的。您也可以运行make+subdir1+subdir2+...。|3007473|#+Register+all+subdirectories+in+the+project's+root+directory.
SUBDIRS+:=+$(wildcard+*/.)

#+Recurse+`make`+into+each+subdirectory.
$(SUBDIRS):+FORCE
++++++++$(MAKE)+-C+$@

#+A+target+without+prerequisites+and+a+recipe,+and+there+is+no+file+named+`FORCE`.
#+`make`+will+always+run+this+and+any+other+target+that+depends+on+it.
FORCE:|code-block|syntax|javascript|3007474|这是另一个具有顶层伪目标的示例：all和clean。请注意，通过$(MAKECMDGOALS)从命令行传递的all和clean目标分别由每个子目录的all和clean目标处理。|3007475|#+Register+all+subdirectories+in+the+project's+root+directory.
SUBDIRS+:=+$(wildcard+*/.)

#+Top-level+phony+targets.
all+clean:+$(SUBDIRS)+FORCE
#+Similar+to:
#+.PHONY:+all+clean
#+all+clean:+$(SUBDIRS)
#+GNU's+.PHONY+target+is+more+efficient+in+that+it+explicitly+declares+non-files.

#+Recurse+`make`+into+each+subdirectory
#+Pass+along+targets+specified+at+command-line+(if+any).
$(SUBDIRS):+FORCE
++++++++$(MAKE)+-C+$@+$(MAKECMDGOALS)

#+Force+targets.
FORCE:|3007476|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/17845120/9730945|1|https://www.gnu.org/software/make/manual/html_node/Force-Targets.html^0|13|6|1I|4|1Z|4|2F|6|2|L|0|2U|C|1|0|0|0|0|0|0|0|0|0|0|0|D|4|12|8|1I|4|2D|O|0|0|G|3|K|5|W|F|1I|3|1M|5|22|3|26|5|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]]|D|@$9|1S|A|1T|1|1U]|$9|1V|A|1W|1|1X]]|E|$]]|$1|F|3|G|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1Z|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|20|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|21|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|22|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|23|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|24|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|25|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|26|8|@]|D|@]|E|$]]|$1|X|3|-4|5|6|7|27|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|28|8|@$9|29|A|2A|B|C]|$9|2B|A|2C|B|C]|$9|2D|A|2E|B|C]|$9|2F|A|2G|B|C]]|D|@]|E|$]]|$1|10|3|11|5|12|7|2H|8|@]|D|@]|E|$13|14]]|$1|15|3|16|5|6|7|2I|8|@$9|2J|A|2K|B|C]|$9|2L|A|2M|B|C]|$9|2N|A|2O|B|C]|$9|2P|A|2Q|B|C]|$9|2R|A|2S|B|C]|$9|2T|A|2U|B|C]|$9|2V|A|2W|B|C]]|D|@]|E|$]]|$1|17|3|18|5|12|7|2X|8|@]|D|@]|E|$13|14]]|$1|19|3|-4|5|6|7|2Y|8|@]|D|@]|E|$]]]|1A|$1B|$5|1C|1D|1E|E|$1F|1G]]|1H|$5|1C|1D|1E|E|$1F|1I]]]]

This is another approach to <a href="https://stackoverflow.com/a/17845120/9730945">MadScientist's answer</a>. <code>.PHONY</code> is a GNU-specific feature that can be used to force <code>make</code> into recursing into each subdirectory. However, some non-GNU versions of <code>make</code> do not support <code>.PHONY</code>, so an alternative is a <a href="https://www.gnu.org/software/make/manual/html_node/Force-Targets.html" rel="noreferrer">force target</a>.

<blockquote>
 4.7 Rules without Recipes or Prerequisites
 
 If a rule has no prerequisites or recipe, and the target of the rule
 is a nonexistent file, then make imagines this target to have been
 updated whenever its rule is run. This implies that all targets
 depending on this one will always have their recipe run.
 
 An example will illustrate this:

<pre><code>clean: FORCE
 rm $(objects)
FORCE:
</code></pre>
 
 Here the target ‘FORCE’ satisfies the special conditions, so the
 target clean that depends on it is forced to run its recipe. There is
 nothing special about the name ‘FORCE’, but that is one name commonly
 used this way.
 
 As you can see, using ‘FORCE’ this way has the same results as using
 ‘.PHONY: clean’.
 
 Using ‘.PHONY’ is more explicit and more efficient. However, other
 versions of make do not support ‘.PHONY’; thus ‘FORCE’ appears in many
 makefiles. See Phony Targets.
</blockquote>

The following is a minimal example that recurses <code>make</code> into each subdirectory, each of which presumably contains a <code>Makefile</code>. If you simply run <code>make</code>, only the first subdirectory, which is non-deterministic, is processed. You may also run <code>make subdir1 subdir2 ...</code>.

<pre class="lang-sh prettyprint-override"><code># Register all subdirectories in the project's root directory.
SUBDIRS := $(wildcard */.)

# Recurse `make` into each subdirectory.
$(SUBDIRS): FORCE
 $(MAKE) -C $@

# A target without prerequisites and a recipe, and there is no file named `FORCE`.
# `make` will always run this and any other target that depends on it.
FORCE:
</code></pre>

Here is another example with top-level phony targets: <code>all</code> and <code>clean</code>. Note that the <code>all</code> and <code>clean</code> targets, passed from command-line via <code>$(MAKECMDGOALS)</code>, are handled by each subdirectory's <code>all</code> and <code>clean</code> targets respectively.

<pre class="lang-sh prettyprint-override"><code># Register all subdirectories in the project's root directory.
SUBDIRS := $(wildcard */.)

# Top-level phony targets.
all clean: $(SUBDIRS) FORCE
# Similar to:
# .PHONY: all clean
# all clean: $(SUBDIRS)
# GNU's .PHONY target is more efficient in that it explicitly declares non-files.

# Recurse `make` into each subdirectory
# Pass along targets specified at command-line (if any).
$(SUBDIRS): FORCE
 $(MAKE) -C $@ $(MAKECMDGOALS)

# Force targets.
FORCE:
</code></pre>

blocks|key|181661|text|您还可以在Makefile中定义一个函数(当然，您还需要在每个子目录中添加一个makefile+)。这是依赖于shell的，但可能很有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181662|define+FOREACH
++++for+DIR+in+packages/*;+do+\
++++++++$(MAKE)+-C+$$DIR+$(1);+\
++++done
endef

.PHONY:+build
build:
++++$(call+FOREACH,build)

.PHONY:+clean
clean:
++++$(call+FOREACH,clean)

.PHONY:+test
test:
++++$(call+FOREACH,test)|code-block|syntax|javascript|181663|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 define a function in the Makefile (also you of course need an additional makefile in each subdirectory). This is shell-dependent, but can be useful:

<pre><code>define FOREACH
 for DIR in packages/*; do \
 $(MAKE) -C $$DIR $(1); \
 done
endef

.PHONY: build
build:
 $(call FOREACH,build)

.PHONY: clean
clean:
 $(call FOREACH,clean)

.PHONY: test
test:
 $(call FOREACH,test)
</code></pre>

blocks|key|3007510|text|关于https://stackoverflow.com/posts/17845120/revisions|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3007511|这是我从那篇文章中学到的。|3007512|顶级Makefile|3007513|#+set+the+default+goal.
#+I+want+the+default+to+really+just+dump+contents+of+dirs
#+as+a+stub.++For+instance,+I+don't+want+it+to
#+push+code+or
.DEFAULT_GOAL+:=+deploy

TOPTARGETS+:=+all+clean

SUBDIRS+:=+docs+src+

$(TOPTARGETS):+$(SUBDIRS)
$(SUBDIRS):
++++echo+"make+arg+is"+$(MAKECMDGOALS)
++++$(MAKE)+-C+$@+$(MAKECMDGOALS)




SUBCLEAN+=+$(addsuffix+.clean,$(SUBDIRS))

clean:+$(SUBCLEAN)

$(SUBCLEAN):+%25.clean:
++++$(MAKE)+-C+$*+clean

deploy:
++++echo+do+deploy+stub|code-block|syntax|javascript|3007514|此Makefile目录共有的src/和docs/都有相应的Makefile。|style|CODE|3007515|以下是文档设置的示例：|3007516|#+set+the+default+goal.
.DEFAULT_GOAL+:=+list_docs



list_docs:
++++ls+-l


clean:
++++echo+"docs:+make+clean"
++++-rm+"*.backup"|3007517|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/posts/17845120/revisions^0|2|1E|0|0|0|0|0|1|8|E|4|J|5|T|8|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|19|8|@$A|1A|B|1B|O|P]|$A|1C|B|1D|O|P]|$A|1E|B|1F|O|P]|$A|1G|B|1H|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1J|8|@]|9|@]|C|$K|L]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

In reference to <a href="https://stackoverflow.com/posts/17845120/revisions">https://stackoverflow.com/posts/17845120/revisions</a>
This is what I learned from that post.
Top Level Makefile
<pre><code># set the default goal.
# I want the default to really just dump contents of dirs
# as a stub. For instance, I don't want it to
# push code or
.DEFAULT_GOAL := deploy

TOPTARGETS := all clean

SUBDIRS := docs src 

$(TOPTARGETS): $(SUBDIRS)
$(SUBDIRS):
 echo &quot;make arg is&quot; $(MAKECMDGOALS)
 $(MAKE) -C $@ $(MAKECMDGOALS)




SUBCLEAN = $(addsuffix .clean,$(SUBDIRS))

clean: $(SUBCLEAN)

$(SUBCLEAN): %.clean:
 $(MAKE) -C $* clean

deploy:
 echo do deploy stub

</code></pre>
The <code>src/</code> and <code>docs/</code> common to this <code>Makefile</code> directory, all have a corresponding <code>Makefile</code>.
Here is an example of the docs setup:
<pre><code># set the default goal.
.DEFAULT_GOAL := list_docs



list_docs:
 ls -l


clean:
 echo &quot;docs: make clean&quot;
 -rm &quot;*.backup&quot;

</code></pre>

I have a directory (<code>root_dir</code>), that contains a number of sub-directories (<code>subdir1, subdir2, ...</code>).
I want to run the <code>make</code> in each directory in <code>root_dir</code>, using a Makefile placed in it.
(Obviously supposed that each of <code>subdir...</code> has inside its own Makefile).
So there are essentially two questions:
<ol>
<li>How to get a list of directories in Makefile (automatically)?</li>
<li>How to run <code>make</code> for each of the directories inside a make file?</li>
</ol>
As I know in order to run <code>make</code> in a specific directory I need to do the following:
<pre><code>$(MAKE) -C subdir
</code></pre>

Run make in each subdirectory

5位重磅专家聚焦 AI 时代开发者核心成长需求，带你深入解锁全栈进化、人机协作关键路径！点击报名到场：<a href="https://cloud.tencent.com/developer/salon/salon-2403/signup" target="_blank">https://cloud.tencent.com/developer/salon/salon-2403/signup</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/487c82639d2338df3ef66dfb1450601a.png"/>

腾讯技术创作特训营「年度论坛」正在报名中！

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个包含许多子目录(subdir1, subdir2, ...)的目录(root_dir)。我想使用放置在其中的Makefile在root_dir中的每个目录中运行make。(显然假设每个subdir...都有自己的Makefile)。所以本质上有两个问题：如何在Makefile (automatically)?H...

问在每个子目录中运行make
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在每个子目录中运行makeEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在每个子目录中运行make
EN