From 2fb819a5498c916865eae8c976434abffc7e0129 Mon Sep 17 00:00:00 2001 From: Leif Andersen Date: Mon, 18 Sep 2023 00:30:58 +0000 Subject: [PATCH] docs: Meson has deprecated the implicit setup command Part-of: --- .../installing/building-from-source-using-meson.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/subprojects/gst-docs/markdown/installing/building-from-source-using-meson.md b/subprojects/gst-docs/markdown/installing/building-from-source-using-meson.md index 914d7a2182..47d450bc3e 100644 --- a/subprojects/gst-docs/markdown/installing/building-from-source-using-meson.md +++ b/subprojects/gst-docs/markdown/installing/building-from-source-using-meson.md @@ -93,14 +93,13 @@ Configuring a module (or several in one go when in gst-build) is done by executing: ``` shell -meson +meson setup ``` The `build_directory` is where all the build instructions and output will be located (This is also called *"out of directory"* building). If the directory is -not created it will be done so at this point. Note that calling `meson` without -any *command* argument is implicitly calling the `meson setup` command (i.e. to -do the initial configuration of a project). +not created it will be done so at this point. Note that older versions of `meson` +could run without any *command* argument, this is now deprecated. There is only one restriction regarding the location of the `build_directory`: it can't be the same as the source directory (i.e. where you cloned your module).