From 4d47ad8ef8add37fc744b179e14170294f07e598 Mon Sep 17 00:00:00 2001 From: Abrar Rahman Protyasha Date: Wed, 17 Mar 2021 01:48:49 +0000 Subject: [PATCH] Fix minor typo in 'Running CMake > Building a project' section --- chapters/intro/running.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/intro/running.md b/chapters/intro/running.md index f28332f..5b04cce 100644 --- a/chapters/intro/running.md +++ b/chapters/intro/running.md @@ -34,7 +34,7 @@ Any *one* of these commands will install: ~/package $ cmake --install build # CMake 3.15+ only {% endterm %} -So set of methods should you use? As long as you *do not forget* to type the build directory as the argument, staying out of the build directory is shorter, and making source changes is easier from the source directory. You should try to get used to using `--build`, as that will free you from using only `make` to build. Note that working from the build directory is historically much more common, and some tools and commands (including CTest) still require running from the build directory. +So which set of methods should you use? As long as you *do not forget* to type the build directory as the argument, staying out of the build directory is shorter, and making source changes is easier from the source directory. You should try to get used to using `--build`, as that will free you from using only `make` to build. Note that working from the build directory is historically much more common, and some tools and commands (including CTest) still require running from the build directory. Just to clarify, you can point CMake at either the source directory *from the build directory*, or at an *existing* build directory from anywhere.