aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2022-08-29 12:06:48 -0400
committerEli Schwartz <eschwartz@archlinux.org>2022-08-29 12:09:52 -0400
commite8d42bd9a829501fe8cfa83cb5bad568d9e24bc9 (patch)
treec5bac40effaeb6c059f3feb3cc77138185ba8947
parentd4733984e9e3970c23a9436dce8919f8a25194e8 (diff)
downloadmeson-e8d42bd9a829501fe8cfa83cb5bad568d9e24bc9.zip
meson-e8d42bd9a829501fe8cfa83cb5bad568d9e24bc9.tar.gz
meson-e8d42bd9a829501fe8cfa83cb5bad568d9e24bc9.tar.bz2
docs: mention in the native-file docs, the command line argument to use
We mention --cross-file in the relevant page, but the fact that --native-file is the command line argument to use is mentioned nowhere other than a couple of release notes and the --help text for meson setup. This should be described in the docs.
-rw-r--r--docs/markdown/Native-environments.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/markdown/Native-environments.md b/docs/markdown/Native-environments.md
index d793132..1253db3 100644
--- a/docs/markdown/Native-environments.md
+++ b/docs/markdown/Native-environments.md
@@ -20,6 +20,13 @@ keep a persistent environment:
* To build with a non-default native tool chain (such as clang instead of gcc)
* To use a non-default version of another binary, such as yacc, or llvm-config
+## Using a native file
+
+During the `setup` phase, use the native file as such:
+```sh
+meson setup --native-file my-native-file.ini builddir/
+```
+
## Changing native file settings
All of the rules about cross files and changed settings apply to native files