From eeebfded853564c4a8c5a6ab7cc6a1d9331b0779 Mon Sep 17 00:00:00 2001 From: Nirbheek Chauhan Date: Tue, 4 Aug 2020 18:39:29 +0530 Subject: Document VS backend from_buildtype behaviour change in release notes Closes https://github.com/mesonbuild/meson/issues/7438 --- docs/markdown/Release-notes-for-0.55.0.md | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'docs/markdown') diff --git a/docs/markdown/Release-notes-for-0.55.0.md b/docs/markdown/Release-notes-for-0.55.0.md index 534c452d7..cd3f79514 100644 --- a/docs/markdown/Release-notes-for-0.55.0.md +++ b/docs/markdown/Release-notes-for-0.55.0.md @@ -305,3 +305,11 @@ $ meson compile "--ninja-args=['a,b', 'c d']" dumping the AST (--ast): **new in 0.55.0** - prints the AST of a meson.build as JSON +## `--backend=vs` now matches `-Db_vscrt=from_buildtype` behaviour in the Ninja backend + +When `--buildtype=debugoptimized` is used with the Ninja backend, the VS CRT +option used is `/MD`, which is the [behaviour documented for all +backends](https://mesonbuild.com/Builtin-options.html#b_vscrt-from_buildtype). +However, the Visual Studio backend was pass `/MT` in that case, which is inconsistent. + +If you need to use the MultiThreaded CRT, you should explicitly pass `-Db_vscrt=mt` -- cgit v1.2.3