aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/snippets
diff options
context:
space:
mode:
authorJussi Pakkanen <jpakkane@gmail.com>2021-01-12 21:51:19 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2021-01-19 20:25:55 +0000
commit8133a7b9a4b8f0686fbc479aa2d64e41c85a979b (patch)
tree6d92574c0b8518e01e5447b3883a8fe3c5d00990 /docs/markdown/snippets
parentc64d4070763b2daf82a50a7b4f5b130b2bb91062 (diff)
downloadmeson-8133a7b9a4b8f0686fbc479aa2d64e41c85a979b.zip
meson-8133a7b9a4b8f0686fbc479aa2d64e41c85a979b.tar.gz
meson-8133a7b9a4b8f0686fbc479aa2d64e41c85a979b.tar.bz2
Keep buildtype the same even if user changes debug and/or optimization.
Diffstat (limited to 'docs/markdown/snippets')
-rw-r--r--docs/markdown/snippets/buildtyperemains.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/markdown/snippets/buildtyperemains.md b/docs/markdown/snippets/buildtyperemains.md
new file mode 100644
index 0000000..4eb6243
--- /dev/null
+++ b/docs/markdown/snippets/buildtyperemains.md
@@ -0,0 +1,10 @@
+## Buildtype remains even if dependent options are changed
+
+Setting the `buildtype' option to a value sets the `debug` and
+`optimization` options to predefined values. Traditionally setting the
+options to other values would then change the buildtype to `custom`.
+This is confusing and means that you can't use, for example, debug
+level `g` in `debug` buildtype even though it would make sense under
+many circumstances. Starting with the buildtype is only changed when
+the user explicitly sets it. Setting the build type sets the other
+options to their default values as before. \ No newline at end of file