Training
Module
Explore Windows architecture - Training
This module provides information about the operating system’s architecture and supported devices. It also describes the desktop support environment and troubleshooting terminology.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This document describes the architectures and operating systems supported by vcpkg.
vcpkg also depends on a few system components to be installed before it can run.
To use vcpkg, a few components need to be installed on the system first.
pkg-config
.
We recommend installing these dependencies via Homebrew, such as via a terminal command
brew install zip unzip curl pkgconfig
.pkg-config
.
We recommend installing these dependencies with your system package manager.
apt install git curl zip unzip pkgconfig
dnf install git curl zip unzip pkgconfig
base-devel git curl zip unzip tar cmake ninja
For Linux and macOS users we also recommend to install the following packages: autoconf
, autoconf-archive
, automake
, make
and libtool
. While not required, these packages are used often by libraries available in vcpkg.
Support is broken into 4 distinct categories. They are:
The fully supported, tested platforms are:
macOS is intended to track the latest version of macOS and contemporary version of Xcode Command Line tools. However, updating macOS machines is a manual process, and macOS frequently changes things in ways that break vcpkg's testing. As of this writing, we are using:
We intend to support AMD64 builds of glibc-based Linuxes still in support from their distribution vendor released within the last 5 years. Examples:
We also assume that users' build systems will match the version of Linux they are using, and take care to ensure components like our manifest mode CMake integration will work with the versions of these dependencies that come with one of the above distros. As of this writing, those dependency versions and the associated distro(s) are:
vcpkg.exe
should work on Windows 7 flavors, but the vast majority of the curated registry requires MSYS2 components
like pkg-config
which
no longer support versions of Windows older than 8.1.
Currently vcpkg has a number of Visual Studio assumptions; in particular our features that copy matching PDBs for executables currently require dumpbin, a Visual Studio component. We have a number of dedicated community members who care about MinGW support though, and do include MinGW toolchains in the box.
On BSD targets, no vcpkg binary is provided for download. Instead, the bootstrap logic will download the vcpkg source code and compile it locally.
vcpkg requires a number of software packages that are not part of the operating system and have to be installed using the package manager:
pkg install -y bash cmake curl git ninja zip unzip
pkg_add -Iz bash cmake coreutils curl git ninja zip unzip-6.10-iconv
As on Linux, it is recommended to also install some additional packages:
pkg install -y autoconf autoconf-archive gmake pkgconf python
pkg_add -Iz autoconf-2.71 autoconf-archive gmake pkgconf python3
unzip
from PATH
. Eventually, this might cause vcpkg to execute the
operating system provided unzip
despite an additional one having been installed using the package manager.
The PATH
environment variable has to be configured to prefer the third party unzip
over the operating system's one,
or vcpkg will fail to extract its binary cache.vcpkg feedback
vcpkg is an open source project. Select a link to provide feedback:
Training
Module
Explore Windows architecture - Training
This module provides information about the operating system’s architecture and supported devices. It also describes the desktop support environment and troubleshooting terminology.