From 8bba5d0a80ece5c14f5e56468dcf50752fe5d46d Mon Sep 17 00:00:00 2001 From: Paolo Bonzini Date: Tue, 26 Aug 2025 10:13:21 +0200 Subject: docs: fix pre-1.8 order for per-subproject options Signed-off-by: Paolo Bonzini --- docs/markdown/Builtin-options.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) (limited to 'docs/markdown') diff --git a/docs/markdown/Builtin-options.md b/docs/markdown/Builtin-options.md index 27efbf2ae..6a3ab85f3 100644 --- a/docs/markdown/Builtin-options.md +++ b/docs/markdown/Builtin-options.md @@ -400,12 +400,17 @@ Between *0.54.0* and *1.7.x* only a few options could be defined per subproject: The value was overridden in this order: -- Value from parent project -- Value from subproject's `default_options` -- Value from `subproject()` `default_options` -- Value from machine file -- Value from command line +- `opt=value` from parent project's `default_options` +- `opt=value` from machine file +- `opt=value` from command line +- `opt=value` from subproject's `default_options` +- `subp:opt=value` from parent project's default options +- `opt=value` from `subproject()` `default_options` +- `subp:opt=value` from machine file +- `subp:opt=value` from command line +In other word, the subproject's `default_options` had a *higher* priority +than `opt=value` from machine file or command line. ## Module options -- cgit v1.2.3