Try to run ninja -t list for example in chromium/src/ directory.
ninja: ERROR: loading 'build.ninja': No such file or directory
But the expected result would be:
browse browse dependency graph in a web browser
clean clean built files
commands list all commands required to rebuild given targets
graph output graphviz dot file for targets
query show inputs/outputs for a path
rules list all rules
targets list targets by their rule or depth in the DAG
return RunTool(tool, &globals, argc, argv);
right before "bool rebuilt_manifest = false;" fixed this issue, but I'm not sure it's the best fix.
Some tools rely on build.ninja being loaded, while a few others don't. I guess I could split the logic.
Fixed in d6ff278 , improved further in d82206d