From e8d42bd9a829501fe8cfa83cb5bad568d9e24bc9 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Mon, 29 Aug 2022 12:06:48 -0400 Subject: [PATCH] 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. --- docs/markdown/Native-environments.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/markdown/Native-environments.md b/docs/markdown/Native-environments.md index d79313224..1253db3d8 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