From 3a4388e51dee5e7e58f1e5ad4e60fb73b4aacf08 Mon Sep 17 00:00:00 2001 From: John Ericson Date: Fri, 2 Aug 2019 14:29:40 -0400 Subject: Fix legacy env var support with cross Fix #3969 --- docs/markdown/snippets/env_vars_and_cross.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/markdown/snippets/env_vars_and_cross.md (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 new file mode 100644 index 0000000..61a63f3 --- /dev/null +++ b/docs/markdown/snippets/env_vars_and_cross.md @@ -0,0 +1,12 @@ +## Environment Variables with Cross Builds + +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_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 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