ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #cmake
Global CMake commands like include_directories leak settings into unrelated targets. Switching to target properties with PRIVATE/INTERFACE/PUBLIC visibility fixes dependency management for good.
Learn how to use CLion and CMake toolchain files to eliminate environment friction when cross-compiling for embedded targets like ARM Cortex-M.
Learn how CLion’s CMake integration lets teams share build configurations via CMakePresets.json, reducing manual setup and keeping IDE indexing in sync with the actual build model.
Decide between FetchContent and ExternalProject_Add in CMake. Compare configuration-time vs. build-time integration with concrete examples for dependency management.
Global include paths pollute builds; target-based CMake replaces them with target properties and PUBLIC PRIVATE INTERFACE visibility keywords.
A technical architecture note on CLion's remote development over SSH, detailing the split-agent design, trust boundaries, and failure-mode adaptations.
Learn how CLion automatically updates its CMake model when you add a library target, what enables instant code completion, and when you may need to reload manually.
Step‑by‑step guide to using CMake’s ExternalProject_Add to automatically fetch, build, and link GoogleTest as a project dependency.
Discover how CMake’s FetchContent can simplify dependency handling, the trade‑offs compared to ExternalProject, a hands‑on fmt example, and practical tips for keeping your build clean and reproducible.
cpp
clion
ssh