From 2d7b7c3aaf23d08d51f375fa1eea80e0ffffed87 Mon Sep 17 00:00:00 2001 From: Dylan Baker Date: Fri, 8 Mar 2024 11:17:58 -0800 Subject: mconf: Reload the options files if they have changed This fixes issues where a new option is added, an option is removed, the constraints of an option are changed, an option file is added where one didn't previously exist, an option file is deleted, or it is renamed between meson_options.txt and meson.options There is one case that is known to not work, but it's probably a less common case, which is setting options for an unconfigured subproject. We could probably make that work in some cases, but I don't think it makes sense to download a wrap during meson configure. --- docs/markdown/snippets/meson_configure_options_changes.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/markdown/snippets/meson_configure_options_changes.md (limited to 'docs') diff --git a/docs/markdown/snippets/meson_configure_options_changes.md b/docs/markdown/snippets/meson_configure_options_changes.md new file mode 100644 index 000000000..c86792ceb --- /dev/null +++ b/docs/markdown/snippets/meson_configure_options_changes.md @@ -0,0 +1,12 @@ +## Meson configure handles changes to options in more cases + +Meson configure now correctly handles updates to the options file without a full +reconfigure. This allows making a change to the `meson.options` or +`meson_options.txt` file without a reconfigure. + +For example, this now works: +```sh +meson setup builddir +git pull +meson configure builddir -Doption-added-by-pull=value +``` -- cgit v1.2.3