blocks|key|1991798|text|我相当确定这将会起作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1991799|make+VERBOSE=1|code-block|syntax|javascript|1991800|您还应该能够将其添加到您的CMakeLists.txt中，以永久设置：|1991801|set(CMAKE_VERBOSE_MAKEFILE+on)|1991802|CMake+FAQ中介绍了这一点。|offset|length|1991803|entityMap|0|LINK|mutability|MUTABLE|url|https://gitlab.kitware.com/cmake/community/wikis/FAQ^0|0|0|0|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

I am fairly sure this will work:

<pre><code>make VERBOSE=1
</code></pre>

You should also be able to add this to your CMakeLists.txt to permanently set that:

<pre><code>set(CMAKE_VERBOSE_MAKEFILE on)
</code></pre>

This is covered in the <a href="https://gitlab.kitware.com/cmake/community/wikis/FAQ" rel="noreferrer">CMake FAQ</a>.

blocks|key|1991821|text|对于automake生成的Makefile，请尝试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1991822|make+V=1|code-block|syntax|javascript|1991823|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|$]]

For automake-generated Makefiles, try:

<pre><code>make V=1
</code></pre>

blocks|key|1778321|text|一个适用于GNU+make并适用于任何Makefile的选项，无论是否由CMake生成，都可以使用--trace选项来生成。这将打印出make正在执行的命令，并且仍然在执行它们。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1778322|这适用于所有命令，而不仅仅是那些在CMake/+V=1生成的makefile中VERBOSE=1或V=1触发打印的命令。|1778323|在Linux上的另一种选择是以strace+-f+-e+trace=execve+make+<make+options>的身份在strace下运行make。strace的输出将包括执行的每个进程:+make、make的shell脚本等等。|1778324|例如，您可能会发现CMake生成的makefile执行/usr/bin/cmake+-E+__run_co_compile+<lots+of+options+...>，但仍然想知道这将运行的确切编译器调用是什么。您可以使用strace方法来实现此目的。|1778325|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Strace^0|1D|7|1V|4|0|O|3|13|9|1D|3|0|F|19|1S|6|0|0|R|1K|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|J|3|K|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

An option, which applies to GNU make and works with any Makefile, whether generated by CMake or not, is to use the <code>--trace</code> option to make. This will print out the commands <code>make</code> is executing and still execute them.

This applies to all commands, not just those that <code>VERBOSE=1</code> or <code>V=1</code> triggers the printing of in CMake/automake generated makefiles.

And yet another alternative on Linux is to run make under <a href="https://en.wikipedia.org/wiki/Strace" rel="nofollow noreferrer">strace</a>, as <code>strace -f -e trace=execve make &lt;make options&gt;</code>. The output from strace will include every process that is executed: by make, by a shell script that make ran, etc.

For instance, you might find that the CMake-generated makefile executes <code>/usr/bin/cmake -E __run_co_compile &lt;lots of options ...&gt;</code> and still wonder what the exact compiler invocation(s) are that this in turn will run. You can get that with the strace method.

I'm working on a large C++ project built with CMake on Linux. CMake runs okay, producing a horde of Makefiles in the tree of modules and applications. Running GNU <code>make</code> leads to linker errors. How can I get <code>make</code> to print out the exact commands before running them?

The -d option does not print the commands, but plenty of information that hasn't been helpful.

The -n option prints all the commands, but does not run them, so I can't tell were exactly the trouble is. Examining the stdout from make -n, I don't see any commands that are relevant. I suspect some commands change depending on the results of earlier commands, and the hierarchy of Makefiles makes it difficult to tell what's really going on.

I don't see any other options in make's man page that seem helpful.

Making CMake print commands before executing

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在做一个在Linux上用CMake构建的大型C++项目。CMake运行良好，在模块和应用程序树中生成了一大堆Makefiles。运行GNU make会导致链接器错误。如何让make在运行命令之前打印出确切的命令？-d选项不会打印命令，但会打印大量没有帮助的信息。-n选项会打印所有命令，但不会运行它们，所以我不能确切...

问在执行前制作CMake打印命令
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在执行前制作CMake打印命令EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在执行前制作CMake打印命令
EN