summaryrefslogtreecommitdiff
path: root/docs/markdown/Release-notes-for-0.54.0.md
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2022-08-16 16:12:35 -0400
committerEli Schwartz <eschwartz@archlinux.org>2022-08-16 16:18:18 -0400
commit25b0988d4e40d22d907169b4f73ff07b4cb7fd0e (patch)
treeb5cdc4588cc1856a00126fb28d09b4fbd1bb9079 /docs/markdown/Release-notes-for-0.54.0.md
parent33a5352e3c56c3d245aed48005515f097ab2ab53 (diff)
downloadmeson-25b0988d4e40d22d907169b4f73ff07b4cb7fd0e.tar.gz
docs: fix various references to "meson builddir"
This is wrong, it should use "meson setup builddir".
Diffstat (limited to 'docs/markdown/Release-notes-for-0.54.0.md')
-rw-r--r--docs/markdown/Release-notes-for-0.54.0.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/markdown/Release-notes-for-0.54.0.md b/docs/markdown/Release-notes-for-0.54.0.md
index 3b060a5a7..f9bfcf6d3 100644
--- a/docs/markdown/Release-notes-for-0.54.0.md
+++ b/docs/markdown/Release-notes-for-0.54.0.md
@@ -120,12 +120,12 @@ value < 1 lets the backend decide how many threads to use. For msbuild
this means `-m`, for ninja it means passing no arguments.
```console
-meson builddir --backend vs
+meson setup builddir --backend vs
meson compile -C builddir -j0 # this is the same as `msbuild builddir/my.sln -m`
```
```console
-meson builddir
+meson setup builddir
meson compile -C builddir -j3 # this is the same as `ninja -C builddir -j3`
```