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 /doc | |
| parent | f66848dbd677b1027bade5728e04954c313231af (diff) | |
Add --dump-scope and --dump-target options to limit --dump output
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manual.cli | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 6f3def4..4583ca0 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -4493,7 +4493,8 @@ buildfile:5:1: dump: The output of \c{dump} might look familiar: in \l{#intro-dirs-scopes Output Directories and Scopes} we've used the \c{--dump} option to print the entire build state, which looks pretty similar. In fact, the \c{dump} directive uses -the same mechanism but allows us to print individual scopes and targets. +the same mechanism but allows us to print individual scopes and targets from +within a \c{buildfile}. There is, however, an important difference to keep in mind: \c{dump} prints the state of a target or scope at the point in the \c{buildfile} load phase @@ -4507,6 +4508,9 @@ a result, while the \c{dump} directive should be sufficient in most cases, sometimes you may need to use the \c{--dump} option to examine the build state just before rule execution. +\N|It is possible to limit the output of \c{--dump} to specific scopes and/or +targets with the \c{--dump-scope} and \c{--dump-target} options.| + Let's now move from state to behavior. As we already know, to see the underlying commands executed by the build system we use the \c{-v} options (which is equivalent to \c{--verbose\ 2}). Note, however, that these are |