docs/modern-cmake
docs/modern-cmake
1
0
Fork 0
mirror of synced 2024-12-22 20:50:00 +01:00
Code Issues Releases Wiki Activity

running.md: mention that CTest 3.19- wants cwd

Browse Source
This commit is contained in:
Alex 2022-06-02 18:28:42 +00:00 committed by Henry Schreiner
parent 8982c92dc6
commit 684f587093
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapters/intro/running.md
View File

@ -35,7 +35,7 @@ Any *one* of these commands will install:
~/package $ cmake --install build # CMake 3.15+ only ~/package $ cmake --install build # CMake 3.15+ only
{% endterm %} {% endterm %}
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. 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 <3.20) 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. Just to clarify, you can point CMake at either the source directory *from the build directory*, or at an *existing* build directory from anywhere.