diff options
Diffstat (limited to 'doc/tutorial/proto.org')
| -rw-r--r-- | doc/tutorial/proto.org | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/tutorial/proto.org b/doc/tutorial/proto.org index 5ab50886..a1eab184 100644 --- a/doc/tutorial/proto.org +++ b/doc/tutorial/proto.org @@ -54,7 +54,7 @@ those would be added to the ~"deps"~ field. When building the library, there's very little to do. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ CONF=$(just-mr -C repos.json setup) $ just build -C $CONF examples address INFO: Requested target is [["@","","examples","address"],{}] @@ -78,7 +78,7 @@ implicitly, when we exploited target-level caching for our external dependencies and did not even construct the dependency graph for that target. A proto library simply provides the dependency structure of the ~.proto~ files. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ just analyse --dump-nodes - -C $CONF examples address INFO: Requested target is [["@","","examples","address"],{}] INFO: Result of target [["@","","examples","address"],{}]: { @@ -177,7 +177,7 @@ The first time, we build a target that requires the proto compiler a bit of time, as the proto compiler has to be built. But in follow-up builds, also in different projects, the target-level cache is filled already. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ just build -C $CONF examples add_person ... $ just build -C $CONF examples add_person @@ -195,7 +195,7 @@ $ If we look at the actions associated with the binary, we find that those are still the two actions we expect: a compile action and a link action. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ just analyse -C $CONF examples add_person --dump-actions - INFO: Requested target is [["@","","examples","add_person"],{}] INFO: Result of target [["@","","examples","add_person"],{}]: { @@ -242,7 +242,7 @@ filled the target-level cache, we can have a look at all targets still analysed. In the one anonymous target, we find again the abstract node we discussed earlier. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ just analyse -C $CONF examples add_person --dump-targets - INFO: Requested target is [["@","","examples","add_person"],{}] INFO: Result of target [["@","","examples","add_person"],{}]: { @@ -332,7 +332,7 @@ the same proto library. And, indeed, analysing the test, we get the expected additional targets and the one anonymous target is reused by both binaries. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ just analyse -C $CONF examples test --dump-targets - INFO: Requested target is [["@","","examples","test"],{}] INFO: Result of target [["@","","examples","test"],{}]: { @@ -388,7 +388,7 @@ $ Finally, the test passes and the output is as expected. -#+BEGIN_SRC shell +#+BEGIN_SRC sh $ just build -C $CONF examples test -Pwork/out.txt INFO: Requested target is [["@","","examples","test"],{}] INFO: Analysed target [["@","","examples","test"],{}] |