aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn Ericson <John.Ericson@Obsidian.Systems>2019-03-21 21:32:35 -0400
committerJohn Ericson <John.Ericson@Obsidian.Systems>2019-03-27 10:54:56 -0400
commit8c3d24e9dea597f8f0a6b0270ce9f80273a707c2 (patch)
treef13f40257451f0564237eea5761e7cdcadf45b4b
parentf53f58f54eaca1e97cc0e3e102ba275c85be60c0 (diff)
downloadmeson-8c3d24e9dea597f8f0a6b0270ce9f80273a707c2.zip
meson-8c3d24e9dea597f8f0a6b0270ce9f80273a707c2.tar.gz
meson-8c3d24e9dea597f8f0a6b0270ce9f80273a707c2.tar.bz2
release note snippet for user flags in sanity checks [skip ci]
-rw-r--r--docs/markdown/snippets/sanity-check.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/docs/markdown/snippets/sanity-check.md b/docs/markdown/snippets/sanity-check.md
new file mode 100644
index 0000000..d5ed80d
--- /dev/null
+++ b/docs/markdown/snippets/sanity-check.md
@@ -0,0 +1,17 @@
+## Sanity checking compilers with user flags
+
+Sanity checks previously only used user-specified flags for cross compilers, but
+now do in all cases.
+
+All compilers meson might decide to use for the build are "sanity checked"
+before other tests are run. This usually involves building simple executable and
+trying to run it. Previously user flags (compilation and/or linking flags) were
+used for sanity checking cross compilers, but not native compilers. This is
+because such flags might be essential for a cross binary to succeed, but usually
+aren't for a native compiler.
+
+In recent releases, there has been an effort to minimize the special-casing of
+cross or native builds so as to make building more predictable in less-tested
+cases. Since this the user flags are necessary for cross, but not harmful for
+native, it makes more sense to use them in all sanity checks than use them in no
+sanity checks, so this is what we now do.