How does Traditional CMake Set-Up work
- Dominant language
- C++
- Stars
- 18.1k
- Forks
- 3.2k
- Avg merge
- 20h 36m
- Merged PRs (30d)
- 1
Description
Update: I can cmake --build targeting /build/abseil-cpp but then it will not find the tests in the next step.
Hello, I am trying to install Abseil for Google S2 Geometry. It leads me to https://github.com/abseil/abseil-cpp/blob/master/CMake/README.md#traditional-cmake-set-up but I'm really confused what am I supposed to do here. I originally followed the quickstart with CMake and installed and passed all the tests. I have installed and built googletest following the command in the link, and then configured Abseil but got stuck at cmake --build /temporary/build/abseil-cpp. It keeps saying /temporary/build/abseil-cpp is not a directory. Thanks in advance.
Contributor guide
Research direction
The issue references the CMake/README.md file and the traditional CMake set-up instructions. Start by reading that documentation to understand the intended build steps. Look at the existing CMake configuration files in the repository to see how the build directory is structured. The goal is to clarify the instructions so that a user can successfully run 'cmake --build' and find the tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100