I have a ninja
build that seems to get stuck at a particular command, however if I run the command manually it completes quickly with no problems.
Is there a way to get ninja
to output more debugging information than ninja -v
so I can work out why it is hanging?
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
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With