diff options
| author | Jussi Pakkanen <jpakkane@gmail.com> | 2019-06-16 22:03:29 +0300 |
|---|---|---|
| committer | Jussi Pakkanen <jpakkane@gmail.com> | 2019-06-16 22:03:29 +0300 |
| commit | 5ecab576673d98b01296ef02c8bc9300c5f6e796 (patch) | |
| tree | 129a6ac8eb27bc09d8a40d31f8e00340763ff251 /docs/markdown/snippets/per-machine-options.md | |
| parent | 288ef0e0e7dbf58a91a1a78095aa51f1bb7a7877 (diff) | |
Update things for new release.0.51.0
Diffstat (limited to 'docs/markdown/snippets/per-machine-options.md')
| -rw-r--r-- | docs/markdown/snippets/per-machine-options.md | 15 |
1 files changed, 0 insertions, 15 deletions
diff --git a/docs/markdown/snippets/per-machine-options.md b/docs/markdown/snippets/per-machine-options.md deleted file mode 100644 index d19c68e90..000000000 --- a/docs/markdown/snippets/per-machine-options.md +++ /dev/null @@ -1,15 +0,0 @@ -## 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. |
