菜单
The modern C++ toolchain at a glance — cmake, ninja, ccache, fast linkers (mold/lld), clang-tools, and package managers (conan/vcpkg) — with a decision framework for when to pin each via mise vs system apt/brew. Use when setting up C++ in a project for the first time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
End-to-end recipe for a modern C++ project managed by mise — cmake + ninja + ccache + mold linker + clang-tools + optional conan package manager. Full CMakePresets.json, mise.toml tasks, and first-run walkthrough. Use when starting a new C++ project or modernizing an existing one.
End-to-end recipe for a Docker-based dev loop with mise — multi-stage Dockerfile with mise pre-installed, docker-compose for services (Postgres, Redis), BuildKit cache mounts, and mise tasks that wrap compose. Use when running dev entirely in containers or prod-parity testing.
End-to-end recipe for a Go HTTP service managed by mise — Go + air (hot reload) + golangci-lint + gotestsum + a Dockerfile hint for production. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new Go service or adding mise to an existing one.
End-to-end recipe for a Neovim configuration managed by mise — the vim.env.PATH prepend pattern, LSPs installed via mise (npm:pyright, aqua:gopls, etc.), conform.nvim for formatters, and the mise-managed "editor as a tool" approach. Use when setting up a modern Neovim config that plays nicely with mise-managed projects.
End-to-end recipe for a Next.js app managed by mise — Node + pnpm (via corepack) + TypeScript + Prettier + ESLint + Playwright. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new Next.js app or adding mise to an existing one.
End-to-end recipe for a FastAPI service managed by mise — Python + uv + ruff + pytest + a Postgres env var. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new FastAPI project or adding mise to an existing one.
| name | mise-cpp-toolchain-overview |
| description | The modern C++ toolchain at a glance — cmake, ninja, ccache, fast linkers (mold/lld), clang-tools, and package managers (conan/vcpkg) — with a decision framework for when to pin each via mise vs system apt/brew. Use when setting up C++ in a project for the first time. |
C++ has no official package manager, no official build system, and no official version-pinning story. That's exactly the gap mise fills: pin your build tooling per-project so every dev and every CI run builds the same way.
| Layer | Tool(s) | Pin via mise? | Why |
|---|---|---|---|
| Compiler | gcc, clang, MSVC | ❌ Usually system | ABI tied to libc/libstdc++; system compiler is safest. Exception: pin clang via aqua:llvm/llvm-project if you need a specific version. |
| Build system generator | cmake, meson | ✅ Yes | Version matters for preset syntax, policies, find_package behavior. |
| Build driver | ninja, make | ✅ ninja yes | ninja is ~2x faster than make for incremental builds; pin via aqua. |
| Compiler cache | ccache, sccache | ✅ Yes | Huge speedup on rebuilds. Pin so CI and dev match. |
| Linker | mold (Linux), lld (Linux/Mac) | ✅ Yes | 10x faster than GNU ld for large projects. |
| Package manager | conan, vcpkg | ⚠️ pipx conan | vcpkg is bootstrapped per-project; conan via pipx (not pip install). |
| Code quality | clang-format, clang-tidy, clangd, iwyu | ✅ Yes | Version matters for format stability and tidy check availability. |
The system-provided versions of cmake and ninja are almost always too old. Ubuntu 22.04 ships cmake 3.22; projects routinely need 3.28+ for C++23 module support. Pinning via mise means:
Compilers are deeply coupled to:
libc — glibc on Linux, musl on alpine, libSystem on macOS).libstdc++ on GCC, libc++ on clang).A mise-installed clang won't necessarily work with your system's libstdc++ (version skew) or your system's debuggers. For most projects, use the system compiler (or a docker image's compiler) and pin everything else via mise.
Exception: if you need a very specific compiler version (building an old kernel, reproducing a CI issue), install it via the OS package manager in a container. Don't try to mise-install GCC.
[tools] block[tools]
cmake = "3.30"
ninja = "1.12"
ccache = "4.10"
"aqua:llvm/llvm-project" = "18" # clangd, clang-format, clang-tidy (optional)
On Linux, add mold. On macOS, add lld (or use Apple's ld-prime; see mise-cpp-linker-fast).
pip. Don't. The pip package is a convenience wrapper that lags the upstream release and isn't trusted for production.CCACHE_DIR set. Cross-project cache pollution. Always scope ccache to the project.CMAKE_GENERATOR=Ninja in [env].mise-cpp-cmake-ninja-ccache — deep dive on the golden trio.mise-cpp-linker-fast — mold vs lld, when each matters.mise-cpp-package-managers — conan 2.x vs vcpkg.mise-cpp-clang-tools — clang-format/tidy/clangd/iwyu setup.mise-host-vs-mise-tools — the general "what belongs in apt vs mise" rule./mise-cpp-init — survey + propose./mise-cpp-bootstrap — one-shot default stack.