From 7924e5f9c20017a0ad7df6ee1cdb540d8a98dff7 Mon Sep 17 00:00:00 2001 From: Jussi Pakkanen Date: Mon, 23 Mar 2020 18:07:24 +0200 Subject: Revert "Naturally use env vars a bit more to match Autoconf" This reverts commit 097dfc085e6a1bb3c670880134a52dcfca504be7. --- docs/markdown/snippets/env_vars_and_cross.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/markdown/snippets') diff --git a/docs/markdown/snippets/env_vars_and_cross.md b/docs/markdown/snippets/env_vars_and_cross.md index f4340de..61a63f3 100644 --- a/docs/markdown/snippets/env_vars_and_cross.md +++ b/docs/markdown/snippets/env_vars_and_cross.md @@ -2,11 +2,11 @@ Previously in Meson, variables like `CC` effected both the host and build platforms for native builds, but the just the build platform for cross builds. -Now `CC` always effects the host platform, and `CC_FOR_BUILD` always affects -the build platform, with `CC` also effecting the build platform for native -builds only when `CC_FOR_BUILD` is not defined. +Now `CC_FOR_BUILD` is used for the build platform in cross builds. This old behavior is inconsistent with the way Autotools works, which undermines the purpose of distro-integration that is the only reason -environment variables are supported at all in Meson. The new behavior is -consistent. +environment variables are supported at all in Meson. The new behavior is not +quite the same, but doesn't conflict: meson doesn't always repond to an +environment when Autoconf would, but when it does it interprets it as Autotools +would. -- cgit v1.1