summaryrefslogtreecommitdiff
path: root/docs/markdown/Tutorial.md
diff options
context:
space:
mode:
authorTheQwertiest <qwertiest@mail.ru>2020-06-15 18:36:08 +0300
committerJussi Pakkanen <jpakkane@gmail.com>2020-06-18 17:47:10 +0300
commit96609da8d26fc05be8845c1edf05c8aa38af047d (patch)
treeb5e5dfdf414d9f9efac2c0743cc211082ef34498 /docs/markdown/Tutorial.md
parente191cbf6e990caa0e912996977584909aab21da8 (diff)
downloadmeson-96609da8d26fc05be8845c1edf05c8aa38af047d.tar.gz
docs: replaced `ninja` with appropriate `meson` commands [skip ci]
Diffstat (limited to 'docs/markdown/Tutorial.md')
-rw-r--r--docs/markdown/Tutorial.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/markdown/Tutorial.md b/docs/markdown/Tutorial.md
index 6b248b519..be6888d6a 100644
--- a/docs/markdown/Tutorial.md
+++ b/docs/markdown/Tutorial.md
@@ -124,12 +124,12 @@ or the like. Instead we just type the exact same command as if we were
rebuilding our code without any build system changes.
```
-$ ninja
+$ meson compile
```
Once you have set up your build directory the first time, you don't
ever need to run the `meson` command again. You always just run
-`ninja`. Meson will automatically detect when you have done changes to
+`meson compile`. Meson will automatically detect when you have done changes to
build definitions and will take care of everything so users don't have
to care. In this case the following output is produced.