From 5ca45669fc714ff2329c92f86e6b09e8ba8d6969 Mon Sep 17 00:00:00 2001 From: Ian Dikhof Date: Mon, 30 Mar 2020 15:46:53 +0000 Subject: [PATCH] fix broken `generator expressions` link --- chapters/basics/functions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chapters/basics/functions.md b/chapters/basics/functions.md index 91f4045..bcd3765 100644 --- a/chapters/basics/functions.md +++ b/chapters/basics/functions.md @@ -30,9 +30,9 @@ There are a variety of keywords as well, such as: * Parentheses can be used to group -## «cmake:Generator-expressions» +## «cmake:generator-expressions» -«cmake:Generator-expressions» are really powerful, but a bit odd and specialized. Most CMake commands happen at configure time, include the if statements seen above. But what if you need logic to occur at build time or even install time? Generator expressions were added for this purpose.[^1] They are evaluated in target properties. +«cmake:generator-expressions» are really powerful, but a bit odd and specialized. Most CMake commands happen at configure time, include the if statements seen above. But what if you need logic to occur at build time or even install time? Generator expressions were added for this purpose.[^1] They are evaluated in target properties. The simplest generator expressions are informational expressions, and are of the form `$`; they evaluate to a piece of information relevant for the current configuration. The other form is `$`, where `KEYWORD` is a keyword that controls the evaluation, and value is the item to evaluate (an informational expression keyword is allowed here, too). If KEYWORD is a generator expression or variable that evaluates to 0 or 1, `value` is substituted if 1 and not if 0. You can nest generator expressions, and you can use variables to make reading nested variables bearable. Some