project_options VS cmake-init

I had been using the project_options repository to bootstrap most of my CMake repositories, but it appears like this is not able to handle Conan2 (due to the usage cmake-conan, on a pre-2.0-compatible version of that repo).

- flags like "-fsanitize=address,leak,undefined -fanalyzer -Wthread-safety -D_FORTIFY_SOURCE=" should be baked in to a default "dev"/"debug" mode newbies shouldn't need to know/think about

Did you try project_options[0]? I recommend it to all newbies like me. Just set the "enable_developer_mode=true" and you get all that stuff for free.

> - I have to Google what headers cstd/std stuff comes from half the time

In Clion you can cmd+click on the symbol and it leads to the header.

Another recommended resource is https://github.com/cpp-best-practices/

[0]: https://github.com/aminya/project_options

https://github.com/friendlyanon/cmake-init This is how you do CMake properly. If you deviate from its install rules you are highly likely to do something wrong.

CMake itself is as declarative as a build systems need to be. For anything nontrivial, these "declarative" solutions all fall apart. Just use https://github.com/friendlyanon/cmake-init, learn CMake and you won't have any issues.

If you want something with a (mostly) Just Works experience then just use https://github.com/friendlyanon/cmake-init

For CMake basics check out the official "Getting started" tutorial: https://cmake.org/cmake/help/latest/guide/tutorial/index.html, as well as Introduction to Modern CMake. You can also get inspired by the CMake project generator cmake-init

You can just use https://github.com/friendlyanon/cmake-init to get a CMake + Conan C project ready to go with a short little command: cmake-init --c -e -p conan coolio