CMake C++ Project taste
# CMake C++ Project taste of a systems developer who wants clean, portable builds - Require a modern CMake (3.24 or newer) and write target-based CMake only, never global `include_directories` or `add_definitions`…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from f.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
# CMake C++ Project taste of a systems developer who wants clean, portable builds - Require a modern CMake (3.24 or newer) and write target-based CMake only, never global `include_directories` or `add_definitions`. Confidence: 0.90 - Attach include paths, flags and definitions to targets with `target_*` commands and the right `PUBLIC`, `PRIVATE` or `INTERFACE` scope. Confidence: 0.90 - Always build out of source, in a `build/` directory that is gitignored. Confidence: 0.95 - Commit a `CMakePresets.json` with debug, release and sanitizer presets so everyone configures the same way. Confidence: 0.85 - Set the language standard with `target_compile_features(... cxx_std_20)` instead of raw `-std=` flags. Confidence: 0.85 - Turn on strict warnings like `-Wall -Wextra -Wpedantic` or `/W4` through a shared interface target, and treat warnings as errors in CI. Confidence: 0.85 - Never use `file(GLOB)` for source lists; list source files explicitly so the build reruns when files change. Confidence: 0.75 - Get third-party libraries with `find_package` backed by vcpkg or Conan, and use `FetchContent` only for small, pinned dependencies. Confidence: 0.80 - Pin every fetched dependency to a tag or commit hash, never a moving branch. Confidence: 0.90 - Never vendor modified copies of libraries without a clear patch file and a note on why. Confidence: 0.75 - Run tests with CTest, and register each test executable with `add_test` or `gtest_discover_tests`. Confidence: 0.85 - Have a CI job that builds with AddressSanitizer and UndefinedBehaviorSanitizer and runs the full test suite. Confidence: 0.85 - Export `compile_commands.json` with `CMAKE_EXPORT_COMPILE_COMMANDS` so clangd and clang-tidy work out of the box. Confidence: 0.90 - Format with a committed `.clang-format` and check it in CI rather than arguing about style in reviews. Confidence: 0.85 - Use Ninja as the default generator for fast incremental builds, and ccache or sccache in CI. Confidence: 0.80 - Provide proper `install()` rules and an exported package config so other projects can use `find_package` on the library. Confidence: 0.75 - Namespace exported targets like `mylib::mylib` and create an alias target with the same name for in-tree use. Confidence: 0.80 - Keep options few and prefixed with the project name, such as `MYLIB_BUILD_TESTS`, and default tests off when used as a subproject. Confidence: 0.75 - Avoid setting `CMAKE_CXX_FLAGS` directly in `CMakeLists.txt`; leave global flags to presets and toolchain files. Confidence: 0.80 - Test the build on Linux, macOS and Windows in CI if the project claims to be portable. Confidence: 0.80
Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
a lot of people even professional said a software product or platfrom especially which has complex rules which was fully coded by AI by a vibe coder who deosnt understand what is the arcture concept deployed, read and…
-
code-hacker
PromptsCode Hacker - VS Code Custom Agent + Web + TUI
Source for code-hacker (opens github.com) git clone https://github.com/hackerlibs/code-hacker.git -
builder prompts which can be sent to builders like cursor, bolt.diy, bolt.new, trae, project idx, Claude code, lovable.dev, llmacoder, geminicoder, windsurf, deepseek-artifact, cline, aider etc
Source for awesome-vibe-coding-prompt-code-templates (opens github.com) git clone https://github.com/KingLeoJr/awesome-vibe-coding-prompt-code-templates.git -
Ethereum Developer
PromptsImagine you are an experienced Ethereum developer tasked with creating a smart contract for a blockchain messenger. The objective is to save messages on the blockchain, making them readable (public) to everyone…
-
Manim Code
PromptsYour task to create a manim code that will explain the chain rule in easy way
-
I’m tired of using Claude Code to build my code because of tokens limits can Ollama build code scripts agentic workflow?