Build and Package Management

Build systems

• CMake documentation: official reference, command docs, and guides for target-based builds.
• Meson documentation: fast build system with a simpler configuration model than some alternatives.

Package managers

• vcpkg: package manager for C and C++ libraries with strong Windows and cross-platform support.
• Conan documentation: modern C/C++ package management and dependency workflow documentation.

Practical guidance

• Prefer CMake when you want the most common cross-platform choice and broad ecosystem support.
• Prefer vcpkg when you want a straightforward dependency flow that integrates well with Windows and CMake.
• Consider Conan when you need more flexible package graph control, profiles, or artifact workflows.
• Consider Meson when you want a more opinionated build setup with a smaller configuration surface.

When to use this page

• starting a new cross-platform C++ project
• adding third-party libraries to a real codebase
• choosing whether your team needs only a build system or also a package manager
• comparing "simple default" versus "more configurable dependency graph"

Quick workflow

1. Start with CMake unless you already know you want a different build system.
2. Add vcpkg when you want a straightforward package flow that works well with common CMake setups.
3. Reach for Conan when dependency version control, profiles, or artifact distribution become important.
4. Use Meson if you prefer a more opinionated build configuration style and it fits your toolchain.