3 ms·

This is quite welcoming. I have tried to digest cmake docs and get so lost. Am I the only one that can’t grok cmake docs? Edit: spelling fixes

• tonetheman 8y ago
  Yeah cmake docs suck. I dig the concept but figuring out how to use it is/was painful. I have not looked in a while. It used to be the only chance you had to learn it was a book you could buy.
• lilott8 8y ago
  The only way I've been able to make any sense of CMake docs is in conjunction with examples -- searching on Github/enormous open source projects using it (e.g. LLVM). Just reading CMake docs to understand how to use directive x almost always leads to failure.
  • mr337 8y ago
    Yup agree, I’m like I know this X project compiles file, let me Look at their cmake file....copy pasta. I’m not proud of it, but it works.
• twic 8y ago
  I found the function-level documentation baffling until i carefully read through the 'buildsystem' documentation, which lays out the fundamental model of how cmake works: https://cmake.org/cmake/help/v3.12/manual/cmake-buildsystem.7.html https://cmake.org/cmake/help/v3.12/manual/cmake-buildsystem.... Its not handholdingly simple, but it is precise and fairly complete, so you have a chance of understanding what is actually going on. All of the tutorials i've seen are just cookbooks with no explanation of how anything works, and mostly describe out-of-date or just plain bad approaches. The rash of "modern cmake" stuff avoids the latter, but really assumes you already know cmake. So that page of documentation was really crucial for me. The 'language' documentation is also helpful: https://cmake.org/cmake/help/v3.12/manual/cmake-language.7.html https://cmake.org/cmake/help/v3.12/manual/cmake-language.7.h...
• blattimwind 8y ago
  Oh no, you're not at all alone. I've actually used CMake as a "how not to do docs" antiexample in the past. More than once, actually.