From 2c90f7cf672ed55d787d2d4372d4a8fc6a45faf2 Mon Sep 17 00:00:00 2001 From: Jesse Bollinger Date: Fri, 23 Oct 2020 16:29:55 +0000 Subject: [PATCH] Fixed a missing parenthesis typo. (PS: I created a GitLab account just to submit this typo fix. The signup process required a lot of needless stuff that wasted a bunch of my time and which has no current relevance whatsoever to what I'm doing e.g. creating a group and project when I have no interest in doing so etc. Perhaps you should switch to a site that has much better understanding of basic user interface/experience design. The experience has definitely left a negative initial impression of GitLab's sense of judgement and taste compared to e.g. GitHub etc.) --- chapters/basics/comms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/basics/comms.md b/chapters/basics/comms.md index d79ec47..1c87153 100644 --- a/chapters/basics/comms.md +++ b/chapters/basics/comms.md @@ -2,7 +2,7 @@ ## Configure File -CMake allows you to access CMake variables from your code using `configure_file`. This command copies a file (traditionally ending in `.in` from one place to another, substituting all CMake variables it finds. If you want to avoid replacing existing `${}` syntax in your input file, use the `@ONLY` keyword. There's also a `COPY_ONLY` keyword if you are just using this as a replacement for `file(COPY`. +CMake allows you to access CMake variables from your code using `configure_file`. This command copies a file (traditionally ending in `.in`) from one place to another, substituting all CMake variables it finds. If you want to avoid replacing existing `${}` syntax in your input file, use the `@ONLY` keyword. There's also a `COPY_ONLY` keyword if you are just using this as a replacement for `file(COPY`. This functionality is used quite frequently; for example, on `Version.h.in`: