From c3b10ee7c9320ed6cf5daec6310b0296812ea86a Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Tue, 15 Nov 2022 17:13:38 +0100 Subject: Make "config" accept a computed target ... and thus allowing the "business logic" in the configuration target (e.g., setting defaults and derived options) to be shared by many targets. --- doc/concepts/built-in-rules.org | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'doc/concepts') diff --git a/doc/concepts/built-in-rules.org b/doc/concepts/built-in-rules.org index 0da0297f..28784193 100644 --- a/doc/concepts/built-in-rules.org +++ b/doc/concepts/built-in-rules.org @@ -125,10 +125,11 @@ map is empty. ** ~"configure"~ -The ~"configure"~ rule allows to configure a target with a given configuration. -Similar to the ~"export"~ rule, the field ~"target"~ must name a single target -(not a list). The ~"config"~ field is evaluated and must result in a map, which -is used as configuration for the given target. +The ~"configure"~ rule allows to configure a target with a given +configuration. The field ~"target"~ is evaluated and the result +of the evaluation must name a single target (not a list). The +~"config"~ field is evaluated and must result in a map, which is +used as configuration for the given target. This rule uses the given configuration to overlay the current environment for evaluating the given target, and thereby performs a configuration transition. It -- cgit v1.2.3