summaryrefslogtreecommitdiff
path: root/doc/tutorial/tests.md
diff options
context:
space:
mode:
authorKlaus Aehlig <klaus.aehlig@huawei.com>2024-05-15 15:57:12 +0200
committerKlaus Aehlig <klaus.aehlig@huawei.com>2024-05-15 15:57:12 +0200
commit2bcbeb55f45a6c5aa193fab06f301f7231d5f16c (patch)
treea1f14009614e44feafe5d16a2293f8703abcbe92 /doc/tutorial/tests.md
parent136e197ee613206d9ae7418054ca18208a63ddcb (diff)
downloadjustbuild-2bcbeb55f45a6c5aa193fab06f301f7231d5f16c.tar.gz
Test tuorial: mention creating a defaults definition for the shell toolchain
... so that the tutorial also works with the latest version of our rules.
Diffstat (limited to 'doc/tutorial/tests.md')
-rw-r--r--doc/tutorial/tests.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/tutorial/tests.md b/doc/tutorial/tests.md
index 72749b0a..cb081594 100644
--- a/doc/tutorial/tests.md
+++ b/doc/tutorial/tests.md
@@ -324,6 +324,21 @@ the `tests/TARGETS` file:
...
```
+A shell test depends on the default settings for the shell. Therefore,
+if we bring our own toolchain defaults for our rules, we have to do this
+here as well. We create the module `shell`
+
+``` sh
+$ mkdir -p ./tutorial-defaults/shell
+```
+
+and create a simple `TARGETS` file saying we are happy with the defaults
+for the defaults.
+
+``` {.jsonc srcname="tutorial-defaults/shell/TARGETS"}
+{"defaults": {"type": "defaults"}}
+```
+
Now we can run the shell test (i.e., build the test result):
``` sh