From 22ef3b55b87cc06bf2016dff1da97f093aa370d5 Mon Sep 17 00:00:00 2001 From: EdsterG Date: Tue, 6 Aug 2019 22:07:19 +0000 Subject: [PATCH] Updated to running.md --- chapters/intro/running.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chapters/intro/running.md b/chapters/intro/running.md index 4de41bf..0ae140e 100644 --- a/chapters/intro/running.md +++ b/chapters/intro/running.md @@ -79,7 +79,7 @@ You can also build just a part of a build by specifying a target, such as the na ## Options -CMake has support for cached options. A Variable in CMake can be marked as "cached", which means it will be written to the cache (a file called `CMakeCache.txt` in the build directory) when it is incountered. You can preset (or change) the value of a cached option on the command line with `-D`. When CMake looks for a cached variable, it will use the existing value and will not overwrite it. +CMake has support for cached options. A Variable in CMake can be marked as "cached", which means it will be written to the cache (a file called `CMakeCache.txt` in the build directory) when it is encountered. You can preset (or change) the value of a cached option on the command line with `-D`. When CMake looks for a cached variable, it will use the existing value and will not overwrite it. ### Standard options @@ -92,5 +92,5 @@ These are common CMake options to most packages: ## Debugging your CMake files -We've already mentioned verbose output for the build, but you can also see verbose CMake configure output too. The `--trace` option will print every line of CMake that is run. Since this is very verbose, CMake 3.7 added `--trace-source="filename"`, which will print out every executed line of just the file you are interested in when it runs. If you select the name of the file you are interested in debugging (usually with a parent directory if you are debugging a CMakeLists.txt, since all of those have the same name), you can just see the lines that run in that file. Very useful! +We've already mentioned verbose output for the build, but you can also see verbose CMake configure output too. The `--trace` option will print every line of CMake that is run. Since this is very verbose, CMake 3.7 added `--trace-source="filename"`, which will print out every executed line of just the file you are interested in when it runs. If you select the name of the file you are interested in debugging (usually by selecting the parent directory when debugging a CMakeLists.txt, since all of those have the same name), you can just see the lines that run in that file. Very useful!