doc: fix confusing use of "build" as a directory argument [skip ci]

In most places, we now refer to "builddir/" which is a lot less likely
to make people think it is a subcommand which needs to be used
literally.

This is a regression since commit 276d342eba
due to the existence of new docs which were added later on, using the
wrong form.
pull/7019/head
Eli Schwartz 4 years ago committed by Dylan Baker
parent c2f647867e
commit 1db800bf67
  1. 12
      docs/markdown/Continuous-Integration.md
  2. 2
      docs/markdown/Release-notes-for-0.55.0.md
  3. 4
      docs/markdown/Release-notes-for-0.56.0.md

@ -221,10 +221,10 @@ jobs:
with:
python-version: '3.x'
- run: pip install meson ninja
- run: meson setup build
- run: meson setup builddir/
env:
CC: gcc
- run: meson test -C build -v
- run: meson test -C builddir/ -v
- uses: actions/upload-artifact@v1
if: failure()
with:
@ -240,10 +240,10 @@ jobs:
python-version: '3.x'
- run: brew install gcc
- run: pip install meson ninja
- run: meson setup build
- run: meson setup builddir/
env:
CC: gcc
- run: meson test -C build -v
- run: meson test -C builddir/ -v
- uses: actions/upload-artifact@v1
if: failure()
with:
@ -258,10 +258,10 @@ jobs:
with:
python-version: '3.x'
- run: pip install meson ninja
- run: meson setup build
- run: meson setup builddir/
env:
CC: gcc
- run: meson test -C build -v
- run: meson test -C builddir/ -v
- uses: actions/upload-artifact@v1
if: failure()
with:

@ -238,7 +238,7 @@ force fallback for specific subprojects.
Example:
```
meson build --force-fallback-for=foo,bar
meson builddir/ --force-fallback-for=foo,bar
```
## Implicit dependency fallback

@ -145,13 +145,13 @@ foo = 'other val'
```
```console
meson build --native-file my.ini
meson builddir/ --native-file my.ini
```
Will result in the option foo having the value `other val`,
```console
meson build --native-file my.ini -Dfoo='different val'
meson builddir/ --native-file my.ini -Dfoo='different val'
```
Will result in the option foo having the value `different val`,

Loading…
Cancel
Save