diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2023-05-02 13:05:27 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2023-05-03 05:03:20 +0200 |
commit | 7a458f210f296cb3cc1551a4606f0cf025003f3a (patch) | |
tree | 71b20a6c67fb9b6801916406391c34e6710c3c2e /libbuild2/b.cli | |
parent | f66848dbd677b1027bade5728e04954c313231af (diff) |
Add --dump-scope and --dump-target options to limit --dump output
Diffstat (limited to 'libbuild2/b.cli')
-rw-r--r-- | libbuild2/b.cli | 28 |
1 files changed, 21 insertions, 7 deletions
diff --git a/libbuild2/b.cli b/libbuild2/b.cli index 5d6ead2..768bcd0 100644 --- a/libbuild2/b.cli +++ b/libbuild2/b.cli @@ -1,8 +1,6 @@ // file : libbuild2/b.cli // license : MIT; see accompanying LICENSE file -include <set>; - include <libbuild2/common.cli>; "\section=1" @@ -774,23 +772,39 @@ namespace build2 \cb{--mtime-check} for details." } - std::set<string> --dump + strings --dump { "<phase>", "Dump the build system state after the specified phase. Valid <phase> values are \cb{load} (after loading \cb{buildfiles}) and \cb{match} - (after matching rules to targets). Repeat this option to dump the - state after multiple phases." + (after matching rules to targets). Repeat this option to dump the state + after multiple phases. By default the entire build state is dumped but + this behavior can be altered with the \c{--dump-scope} and + \cb{--dump-target} options." + } + + dir_paths --dump-scope + { + "<dir>", + "Dump the build system state for the specified scope only. Repeat this + option to dump the state of multiple scopes." + } + + vector<pair<name, optional<name>>> --dump-target + { + "<target>", + "Dump the build system state for the specified target only. Repeat this + option to dump the state of multiple targets." } - std::vector<name> --trace-match + vector<name> --trace-match { "<target>", "Trace rule matching for the specified target. This is primarily useful during troubleshooting. Repeat this option to trace multiple targets." } - std::vector<name> --trace-execute + vector<name> --trace-execute { "<target>", "Trace rule execution for the specified target. This is primarily useful |