From 6570ad817d9e84c5a65e84896aff658317e7f944 Mon Sep 17 00:00:00 2001 From: Mehran prs Date: Thu, 30 Mar 2023 12:19:53 +0000 Subject: [PATCH] docs: fix typo --- chapters/features/utilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/features/utilities.md b/chapters/features/utilities.md index fe4178f..95a65fd 100644 --- a/chapters/features/utilities.md +++ b/chapters/features/utilities.md @@ -81,7 +81,7 @@ There is a boolean target property, `LINK_WHAT_YOU_USE`, that will check for ext ## Clang-format -Clang-format doesn't really have an integration with CMake, unfortunately. You could make a custom target (See [this post](https://arcanis.me/en/2015/10/17/cppcheck-and-clang-format), or you can run it manually. An interesting project that I have not really tried is [here](https://github.com/kbenzie/git-cmake-format); it adds a format target and even makes sure that you can't commit unformatted files. +Clang-format doesn't really have an integration with CMake, unfortunately. You could make a custom target (See [this post](https://arcanis.me/en/2015/10/17/cppcheck-and-clang-format)), or you can run it manually. An interesting project that I have not really tried is [here](https://github.com/kbenzie/git-cmake-format); it adds a format target and even makes sure that you can't commit unformatted files. The following two line would do that in a git repository in bash (assuming you have a `.clang-format` file):