An introduction to the build pipeline, and how we can orchestrate it manually

Before working with CMake, it's useful to understand the tools it orchestrates. This lesson guides you through setting up a C++ toolchain.

Building C++ Programs

Walking through the steps of the C++ compilation process, from source code to machine code.

The Compilation Pipeline

The linker's role in the build process, how it resolves symbols to combine object files, and how to troubleshoot common errors.

Object Files and the Linking Process

The difference between static and dynamic libraries, how to create them, and the trade-offs between them.

Static and Shared Libraries

The C++ Build Process

Recommended approaches for managing large projects and the libraries that they depend on

Learn how to structure your C++ projects for scalability and maintainability, from basic directory layouts to managing multiple modules.

Organizing a C++ Project

Learn to manage third-party libraries in C++, covering include/library paths, static vs. shared libraries, versioning, and platform differences.

Managing Libraries and Dependencies

An introduction to traditional build tools like Makefiles and IDE projects, highlighting the maintenance, scalability, and cross-platform challenges that result

Automated Build Systems and Their Limitations

Project Structure and Dependency Management

Setting up CMake and creating your first project

An introduction to CMake, the cross-platform, open-source meta-build system that solves the core challenges of C++ project management.

Why CMake?

A step-by-step guide to installing CMake. We'll explore command-line, GUI, and IDE workflows, and how to configure your compiler.

Setting Up a CMake Environment

Creating the bare minimum `CMakeLists.txt` file and build up to a project with an executable and a library, learning the fundamental commands along the way.

Writing a CMakeLists File

Learn the two-stage process of building a CMake project. This lesson covers configuring, generating, building, running, and troubleshooting common errors.

Building and Running CMake Projects

Learn how to organize large C++ projects in CMake using subdirectories and the `add_subdirectory()` command to create modular, maintainable builds.

CMake Project Structure and Subdirectories

Introducing CMake

Exploring CMake's programming features, caching mechanisms, and interactions with the file system

A primer on the fundamental building blocks of the CMake language: variables, string interpolation, and logging messages.

CMake Variables and Logging

Discover the CMake Cache, the mechanism for storing persistent user-configurable options, and learn how to create and manage cached variables.

The CMake Cache

Exploring CMake's command syntax and its list data type, including how to create, manipulate, and use lists in your projects.

CMake Commands, Arguments, and Lists

Transform your static build descriptions into dynamic scripts with CMake's control flow commands, if() and foreach().

CMake Conditionals and Loops

Exploring CMake's `file()` command, covering how to read, write, copy, and glob files, and how to manipulate paths.

Working with the File System

Learn to create reusable logic with CMake functions and macros, and how to organize them into modules for clean, scalable build systems.

Modularizing CMake Code

CMake Language and Fundamentals

Learn more about targets, and how their properties and links are the foundation of modern CMake

Learn to work with target properties - understanding their purpose, setting and updating them, and retrieving them when your build requires it

Target Properties

Learn about target types, and how the `PUBLIC`, `PRIVATE`, and `INTERFACE` keywords control how properties are shared.

Relationships Between Targets

Discover how CMake's `target_link_libraries()` command builds a dependency graph, and how it uses this graph to automatically manage transitive dependencies and link order.

Indirect Relationships and the Dependency Graph

Learn to use abstract target types like `INTERFACE`, `ALIAS`, and `IMPORTED` to model complex project needs, organize build properties, and integrate pre-compiled binaries.

Using `INTERFACE`, `ALIAS`, and `IMPORTED` Libraries

Adding support for user-configurable library types and an initial introduction to target installation.

Using Shared Libraries

Targets and Dependencies

Learn how to manage multiple build configurations within the same project, and how to create scripts that adapt to the environment

Learn how CMake manages different build configurations like Debug and Release, the difference between generator types, and how to apply settings conditionally using modern techniques.

Build Configurations (Debug, Release, etc.)

Learn the tools and patterns needed to write portable CMakeLists.txt files that work seamlessly across platforms and compilers

Cross-Platform Configurations

Learn to write architecture-aware CMake scripts for 32/64-bit systems and Apple's Universal Binaries (Intel/ARM).

Handling Different Architectures

Learn to build for different operating systems and architectures using CMake's cross-compilation support and toolchain files.

Cross-Compilation and Toolchain Files

Platforms and Build Configurations

Learn how to add external libraries to our build, and how to create our own packages for others to use

Learn to find and use pre-installed libraries with `find_package()`, understanding Module vs. Config mode and the power of imported targets

Finding Dependencies using `find_package()`

Learn how to make your libraries consumable by other projects using CMake by turning your build-tree into a distributable install-tree.

Creating a Consumable Package

Learn how to consume a CMake package you've installed, completing the producer-consumer cycle. We'll cover using `find_package()` and how to point CMake to your library's location

Using Installed Packages

Learn how to create self-contained, reproducible builds by fetching dependencies from source using `FetchContent()` and `ExternalProject_Add()`.

Fetching External Dependencies

Creating and Consuming Packages

Integrating the vcpkg and Conan package managers to handle external dependencies

Learn to manage C++ dependencies effortlessly with the vcpkg package manager and its seamless CMake integration using toolchain files and manifests.

Integrating CMake and vcpkg

Learn the day-to-day commands for managing dependencies with vcpkg and how to guarantee reproducible builds using baselines and version overrides

vcpkg Commands and Versioning

Combine vcpkg with CMake's cross-compilation capabilities. Learn to use triplets to target different architectures and chain-load toolchain files

Cross-Compiling with vcpkg

Discover Conan, the binary-first C++ package manager, and learn how to integrate it with CMake using profiles and lockfiles for fast, reproducible builds.

Using Conan with CMake

Learn to cross-compile C++ projects with Conan, using build and host profiles to manage dependencies for different platforms.

Cross-Compilation with Conan

Package Managers

Introducing presets, allowing us to simplify our workflow and share common configurations across our team

Learn the fundamentals of CMake Presets. This lesson introduces `CMakePresets.json` to simplify complex build commands.

CMake Presets

Learn to structure your CMake presets with inheritance and customize them for your local environment using `CMakeUserPresets.json`.

User Presets and Inheritance

Learn to make your CMake presets portable by using environment variables and conditional logic to adapt to different machine configurations.

Environment Variables and Conditional Presets

Learn how to extend the build process beyond simple compilation by integrating external tools and custom commands

Learn how to use generator expressions `$<...>` for build-time conditional logic.

Generator Expressions and Conditional Logic

Learn how to attach commands to specific points in a target's build lifecycle using `add_custom_command(TARGET)` for tasks like post-build file copying.

Integrating Tools with `add_custom_command()`

Learn to integrate code generators like Protobuf into your build process using `add_custom_command()`, creating automated file-level dependencies in CMake.

Generating Files with Protobuf and `add_custom_command()`

Custom Commands

An introduction to automating common workflow chores by creating custom targets

Learn to create standalone, non-code targets using add_custom_target() for utility tasks like code formatting and documentation generation.

Custom Targets and Build Utilities

Using the Clang-Format tool to automatically enforce a consistent coding style, and integrating it into our build using a custom CMake target

Using Clang-Format

An introduction to file sets and the `target_sources()` command, allowing us to manage our header files in a more controlled way

Using File Sets

A step-by-step guide to integrating Doxygen into your CMake build process for automated C++ documentation.

Generating Documentation with Doxygen

Custom Targets

Integrate automated tests into a CMake project using CTest, GoogleTest, and GoogleMock

Learn the fundamentals of automated testing in C++ with CTest. Create your first test suite, register tests with `add_test()`, and run them with the `ctest` command.

Automated Testing and CTest

Learn to refactor manual C++ tests into a professional test suite using the GoogleTest framework, managed by vcpkg and integrated with CTest.

Integrating GoogleTest with CMake

Learn to use a wide range of assertions, write data-driven parameterized tests, and isolate dependencies with Google Mock.

Assertions and Parameterized Tests

Learn how to isolate dependencies that our project uses, and then how to replace those dependencies at test time using Google Mock.

Dependency Injection and Mocking

Learn the standard pattern for testing application logic by refactoring it into a linkable library

Testing Executables

Move beyond individual tests to manage a full test suite. Learn to organize tests, run tests in parallel, filter by labels, and measure our code coverage

Managing a Test Suite

Automated Testing

Using static and dynamic analysis in CMake projects to automatically detect memory bugs, performance issues, and problematic code

Learn to find memory bugs at runtime by integrating AddressSanitizer (ASan) into a CMake project

Using AddressSanitizer (ASan)

Adding benchmarks to our build to measure the performance of our code, and track how it changes over time

Using Google Benchmark

Integrating Clang-Tidy to enforce good practices and find bugs before we even compile

Using Clang-Tidy

Automated Analysis

Automating the entire development lifecycle using Git for souce control, GitHub Actions for cloud builds, and CPack to create distributable packages and installers.

An introduction to Git, the version control system that underpins modern collaborative software development and automated build pipelines.

Source Control with Git

Learn how to automate your build and test process with Continuous Integration (CI) and a build server. This lesson provides a guide to creating a GitHub Actions workflow for a CMake project.

Build Servers and Continuous Integration

Learn to package your C++ projects using CMake's CPack. This lesson covers creating developer ZIP archives and professional Windows MSI installers with components.

Packaging with CPack

Learn to automate the packaging process by integrating CPack with a multi-platform GitHub Actions workflow

Packaging with GitHub Actions

Learn to automate the creation of a professional Windows installer by integrating CPack, the WiX Toolset, and a multi-platform GitHub Actions workflow.

Creating Installers with CPack and GitHub Actions

Learn to automate the release process using a GitHub Actions workflow that builds, packages, and publishes artifacts to a GitHub Release

Deployment with GitHub Releases

Continuous Integration and Packaging

If you have a basic grasp of C++ but find the build process intimidating, this course is for you. We assume you know the language, but not how to manage large projects.

Manage complex, cross-platform builds using industry-standard tools. Create scalable build systems that automate the entire development lifecycle.

This course is a comprehensive deep-dive into the entire C++ build ecosystem, centered around the power and flexibility of modern CMake. We leave no stone unturned.

Start with a foundational understanding of compilers, linkers, static vs. shared libraries, and object files.

The Full Build Pipeline

Learn every aspect of the CMake language, from variables and control flow to functions, modules, and generator expressions.

Complete CMake Language Mastery

Master the modern target-centric paradigm, including properties, usage requirements, and abstract targets.

Advanced Target Management

Explore every method for handling dependencies, from `find_package` and `FetchContent` to vcpkg and Conan, including versioning and cross-compilation.

In-Depth Dependency Management

Integrate a full suite of professional tools for testing (CTest, GoogleTest), analysis (ASan, Clang-Tidy), and packaging (CPack).

Total Workflow Automation

Build a fully automated deployment pipeline that takes your code from a Git push to a published GitHub Release with multi-platform installers.

End-to-End CI/CD and Deployment

What You'll Learn

Become a software engineer with C++.  Starting from the basics, we guide you step by step along the way

Intro to C++ Programming

If you're completely new to programming or want a thorough introduction, consider starting with our free introductory course:

New to Programming?

Managing C++ Projects Using CMake

In our <InlineLessonPromo url="cmake/cross-compilation-and-toolchain-files" title="Cross-Compilation and Toolchain Files" description="Learn to build for different operating systems and architectures using CMake's cross-compilation support and toolchain files.">cross-compilation lessons</InlineLessonPromo>, we learned that the primary mechanism we use to tell CMake about our target is via the `CMAKE_TOOLCHAIN_FILE`.  However, we've also just learned that vcpkg uses this same mechanism to teach CMake how to use it. So what happens when you need to cross-compile a project using vcpkg?


To solve this, we use a technique called chain loading - where each toolchain file loads the next toolchain file, until we have loaded everything we need.


## Practical Example


Let's revisit an earlier example, where we were building a Windows application on a macOS host.  Our cross-compilation toolchain file looked like this:


<CodeFile path="toolchains/mingw-windows-x64.cmake">


```c++
#<cmake>
# 1. Set the target system
set(CMAKE_SYSTEM_NAME Windows)
set(CMAKE_SYSTEM_PROCESSOR x86_64)

# 2. Specify the cross-compilers
set(CMAKE_C_COMPILER x86_64-w64-mingw32-gcc)
set(CMAKE_C_FLAGS_INIT "-static-libgcc")

set(CMAKE_CXX_COMPILER x86_64-w64-mingw32-g++)
set(CMAKE_CXX_FLAGS_INIT
  "-static-libgcc -static-libstdc++")

set(CMAKE_EXE_LINKER_FLAGS_INIT
  "-static-libgcc -static-libstdc++")

# 3. Configure search for external dependencies
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
```


</CodeFile>


We'll update our minimalist Windows application from earlier to now have it log out to a file.  We'll use features provided by spdlog, which is still being provided by vcpkg and `find_package()` from the previous lesson:


<CodeViewer>


<CodeFile path="app/src/main.cpp" defaultOpen>


```c++
#include <windows.h>
#include <spdlog/spdlog.h>//<h>

int WINAPI WinMain(HINSTANCE, HINSTANCE, LPSTR, int) {
  auto logger{spdlog::basic_logger_mt(//<h>
    "file_logger", "log.txt"//<h>
  )};//<h>
  logger->info("Program started");//<h>

  MessageBox(
    nullptr,
    "I was cross-compiled from a Mac!",
    "Hello Windows",
    MB_OK
  );
  
  logger->info("Program shut down");//<h>
  
  // Flush logs to ensure they're written
  spdlog::shutdown();//<h>
  
  return 0;
}
```


</CodeFile>


<CodeFile path="vcpkg.json">


```json
{
  "dependencies": [
    "spdlog"//<h>
  ]
}
```


</CodeFile>


<CodeFile path="app/CMakeLists.txt">


```c++
#<cmake>
cmake_minimum_required(VERSION 3.16)

add_executable(GreeterApp src/main.cpp)

find_package(spdlog CONFIG REQUIRED) #<h>

target_link_libraries(GreeterApp
  GreeterLib
  spdlog::spdlog#<h>
)
```


</CodeFile>


</CodeViewer>


### The `VCPKG_TARGET_TRIPLET` and `MINGW` Variables


When we bootstrapped vcpkg as part of our installation, it automatically scanned our environment to determine it's architecture.


For example, if we're on a recent Mac, vcpkg is probably assuming we want to use `arm64-osx` libraries.  You can check this by viewing the `VCPKG_TARGET_TRIPLET` variable:


```c++
#<cmake>
message(STATUS "VCPKG triplet: ${VCPKG_TARGET_TRIPLET}")
```


```c++
//<o>
-- VCPKG triplet: arm64-osx
```


After running the configure step, we can also check which libraries vcpkg built within the `status` file:


<CodeFile path="build/vcpkg_installed/vcpkg/status">


```c++
Package: fmt
Version: 11.2.0
Depends: vcpkg-cmake, vcpkg-cmake-config
Architecture: arm64-osx//<w>
...

Package: spdlog
Version: 1.15.3
Depends: fmt, vcpkg-cmake, vcpkg-cmake-config
Architecture: arm64-osx//<w>
...
```


</CodeFile>


These `arm64-osx` libraries won't work when cross compiling to Windows, so we need to change this `VCPKG_TARGET_TRIPLET` variable.  Things we want to override for our target are in our toolchain file, so that's where we'll update this value.


Our toolchain file is designed for using MinGW, so it should set the triplet to `x64-mingw-dynamic` for dynamic libraries (DLL), or `x64-mingw-static` if we want to use static linking.  We should also set a `MINGW` variable to true, as this improves the behavior of vcpkg's toolchain file once we load it:


<CodeFile path="toolchains/mingw-windows-x64.cmake">


```c++
#<cmake>
# Previous configuration is unchanged
# 1. Set the target system
set(CMAKE_SYSTEM_NAME Windows)
set(CMAKE_SYSTEM_PROCESSOR x86_64)

# 2. Specify the cross-compilers
set(CMAKE_C_COMPILER x86_64-w64-mingw32-gcc)
set(CMAKE_C_FLAGS_INIT "-static-libgcc")

set(CMAKE_CXX_COMPILER x86_64-w64-mingw32-g++)
set(CMAKE_CXX_FLAGS_INIT
  "-static-libgcc -static-libstdc++")

set(CMAKE_EXE_LINKER_FLAGS_INIT
  "-static-libgcc -static-libstdc++")

# 3. Configure search for external dependencies
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

# New Additions
set(MINGW TRUE)#<h>
set(VCPKG_TARGET_TRIPLET x64-mingw-static)#<h>
```


</CodeFile>


### Chain Loading


We still have to solve the problem where our configuration is spread across two toolchain files - the one we created to define our cross-compilation target, and the one that vcpkg provided.


To solve this, we simply update our toolchain file to `include()` the vcpkg one.  Remember to update `/path/to/vcpkg` to use whatever directory vcpkg is installed in on your system:


<CodeFile path="toolchains/mingw-windows-x64.cmake">


```c++
#<cmake>
# Previous configuration is unchanged
# 1. Set the target system
set(CMAKE_SYSTEM_NAME Windows)
set(CMAKE_SYSTEM_PROCESSOR x86_64)

# 2. Specify the cross-compilers
set(CMAKE_C_COMPILER x86_64-w64-mingw32-gcc)
set(CMAKE_C_FLAGS_INIT "-static-libgcc")

set(CMAKE_CXX_COMPILER x86_64-w64-mingw32-g++)
set(CMAKE_CXX_FLAGS_INIT "-static-libgcc -static-libstdc++")

set(CMAKE_EXE_LINKER_FLAGS_INIT "-static-libgcc -static-libstdc++")

# 3. Configure the search behavior for external dependencies
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

# New Additions
set(MINGW TRUE)
set(VCPKG_TARGET_TRIPLET x64-mingw-static)
include("/path/to/vcpkg/scripts/buildsystems/vcpkg.cmake")#<h>
```


</CodeFile>


Note that the ordering of this file is important - we set the `MINGW` and `VCPKG_TARGET_TRIPLET` variables **before** we `include()` the `vcpkg.cmake` file, such that the commands within that file can read the correct value.


Now, when we tell CMake to use our toolchain file (by setting `CMAKE_TOOLCHAIN_FILE` to it's path), this file will then chain load the vcpkg one, meaning our build will use both.


This isn't portable right now, as we have hardcoded the location of vcpkg within our specific system, which is unlikely to work for others.  The main way to solve problems like this is by using **environment variables**, which we'll cover later in the course.


### Building and Testing


Now that everything is set up, let's try to configure and build our project from a **clean** `/build` directory:


```c++
//<ti>
cmake .. -DCMAKE_TOOLCHAIN_FILE="../toolchains/mingw-windows-x64.cmake"
```


```c++
//<ti>
cmake --build .
```


If the build succeeded, we can run our application on Windows or an emulator to confirm that everything worked:


<Img hasTransparency file="cmake-cross-compile-output.png" alt="Diagram showing our cross-compiled program running natively and in an emulator" width="1200" height="496" blurHash="L.LXVzofofj[~qoffkay9FfRayay" />


We should also see that spdlog created a log file next to our executable:


<CodeFile path="log.txt">


```c++
//<nh>
[2025-08-19 16:12:23.481] [file_logger] [info] Program started
[2025-08-19 16:12:35.050] [file_logger] [info] Program shut down
```


</CodeFile>


<Pw>


## Chain Loading Using vcpkg


In the previous example, we had our toolchain file chain load vcpkg's version, but we can also do this in the opposite direction and have vcpkg load our toolchain file.


For this workflow, we should first remove the `include()` command from our toolchain file:


<CodeFile path="toolchains/mingw-windows-x64.cmake">


```c++
#<cmake>
# 1. Set the target system
set(CMAKE_SYSTEM_NAME Windows)
set(CMAKE_SYSTEM_PROCESSOR x86_64)

# 2. Specify the cross-compilers
set(CMAKE_C_COMPILER x86_64-w64-mingw32-gcc)
set(CMAKE_C_FLAGS_INIT "-static -static-libgcc")

set(CMAKE_CXX_COMPILER x86_64-w64-mingw32-g++)
set(CMAKE_CXX_FLAGS_INIT
  "-static -static-libgcc -static-libstdc++")

set(CMAKE_EXE_LINKER_FLAGS_INIT
  "-static-libgcc -static-libstdc++")

# 3. Configure the search for external dependencies
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

set(VCPKG_TARGET_TRIPLET x64-mingw-static)#<d>
set(MINGW TRUE)#<d>
include("/path/to/vcpkg/scripts/buildsystems/vcpkg.cmake")#<d>
```


</CodeFile>


The vcpkg toolchain file looks for a `VCPKG_CHAINLOAD_TOOLCHAIN_FILE` variable which, if defined, it will chain load.


We can set this variable however we like, but let's do it on the command line this time.  This means our terminal command needs two arguments:

1. `CMAKE_TOOLCHAIN_FILE`: The path to the `vcpkg.cmake` file that we just removed from our toolchain
2. `VCPKG_CHAINLOAD_TOOLCHAIN_FILE`: The path to our `mingw-windows-x64.cmake` toolchain file.

Running from our `/build` directory, the command will look something like below, where you have updated the `/vcpkg/` and `/project` strings with the location of your vcpkg and project directories:


Note the `\` characters let us add line breaks to a complex command for presentational reasons.  The underlying terminal will still treat the input as a single command:


```c++
//<ti>
cmake .. \
  -DCMAKE_TOOLCHAIN_FILE=\
    "/vcpkg/scripts/buildsystems/vcpkg.cmake" \
  -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=\
    "/project/toolchains/mingw-windows-x64.cmake"
```


This approach is more portable than our earlier example of hardcoding our `/path/to/vcpkg` in our `CMakeLists.txt` file.


However, this is a horrendously long and error-prone command - it is not something we want to be inputting often.  In the next chapter, we'll learn how to save combinations of configuration values like this to a `CMakePresets.json` file where they can be applied and shared more easily.


For now, though, either of these two approaches to chainloading allow us to combine vcpkg's dependency management with CMake's native cross-compilation support.


## Summary


This lesson combined our knowledge of CMake toolchains with the power of vcpkg package management workflow. Both vcpkg and a cross-compilation setup need to be configured via the `CMAKE_TOOLCHAIN_FILE`, creating a conflict.


The solution to the toolchain conflict is to "chain" the files together. There are two main approaches:

1. Have your custom toolchain file `include()` the `vcpkg.cmake` file.
2. Use the `vcpkg.cmake` toolchain and set the `VCPKG_CHAINLOAD_TOOLCHAIN_FILE` variable to point to your custom toolchain. This is generally more flexible, but requires more complex configuration commands.  We'll solve the complex command problem using presets in the next chapter.

We also learned that vcpkg uses "triplets" to define a target architecture (e.g., `x64-mingw-static`). We tell vcpkg which triplet to use by setting the `VCPKG_TARGET_TRIPLET` variable, which instructs it to build dependencies for our target platform, not our host.


<Preview>


### An Alternative: Conan


vcpkg is a fantastic, modern tool that integrates beautifully with CMake. However, it's not the only player in the game. Another extremely popular and powerful C++ package manager is **Conan**.


While vcpkg focuses on integrating from source with a central repository, Conan offers a more decentralized model, with a powerful binary management system that is highly favored in corporate environments.


In the next lesson, we will explore Conan, see how its philosophy differs from vcpkg, and learn how to integrate it into our CMake projects.


</Preview>


</Pw>

Vendoring and Fetching Dependencies

Package Managers Integration (Conan)

vcpkg Homepage

vcpkg: A C++ package manager for Windows, Linux, and macOS

Manifest mode

CMake Toolchains

vcpkg: The C++ Library Manager for Everyone - Robert Schumacher & Augustin Popa

vcpkg GitHub Repository

Learn how to cross-compile C++ projects using vcpkg and CMake. This tutorial covers triplets for targeting different platforms, and how to chain-load toolchain files to combine vcpkg's dependency management with your cross-compiler.

Cross-Compilation with vcpkg and CMake: Triplets and Toolchains

The `VCPKG_TARGET_TRIPLET` and `MINGW` Variables

Cross-Compiling with vcpkg

Understanding the Basics

Practical Applications

Common Mistakes

Next Steps

Additional Resources

Assessment Preparation

Managing C++ Projects Using CMake