From af2d7af9983a04fa2dd6c073bdc41847a23012c8 Mon Sep 17 00:00:00 2001 From: John Ericson Date: Mon, 15 Apr 2019 01:23:10 -0400 Subject: Per machine do 'build.' and '' option prefixes See the docs/ changes for details. --- docs/markdown/snippets/per-machine-options.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 docs/markdown/snippets/per-machine-options.md (limited to 'docs/markdown/snippets') diff --git a/docs/markdown/snippets/per-machine-options.md b/docs/markdown/snippets/per-machine-options.md new file mode 100644 index 0000000..d19c68e --- /dev/null +++ b/docs/markdown/snippets/per-machine-options.md @@ -0,0 +1,15 @@ +## Specifying options per mer machine + +Previously, no cross builds were controllable from the command line. +Machine-specific options like the pkg-config path and compiler options only +affected native targets, that is to say all targets in native builds, and +`native: true` targets in cross builds. Now, prefix the option with `build.` to +affect build machine targets, and leave it unprefixed to affect host machine +targets. + +For those trying to ensure native and cross builds to the same platform produced +the same result, the old way was frustrating because very different invocations +were needed to affect the same targets, if it was possible at all. Now, the same +command line arguments affect the same targets everwhere --- Meson is closer to +ignoring whether the "overall" build is native or cross, and just caring about +whether individual targets are for the build or host machines. -- cgit v1.1