我有一个ninja
构建,似乎卡在了某个特定命令上,但是,如果我手动运行该命令,它会很快完成而不会出现问题。
是否有一种方法可以使ninja
输出比ninja -v
更多的调试信息,所以我可以弄清楚为什么它挂了?
答案 0 :(得分:1)
prebuilts/build-tools/linux-x86/bin/ninja -d list
debugging modes:
stats print operation counts/timing info
explain explain what caused a command to execute
keepdepfile don't delete depfiles after they're read by ninja
keeprsp don't delete @response files on success
multiple modes can be enabled via -d FOO -d BAR