The latest version of this documentation is available on GitHub.
Buildsystem Integration
vcpkg integrate [options] install
vcpkg integrate [options] remove
vcpkg integrate [options] project
Shell Integration
vcpkg integrate [options] powershell
vcpkg integrate [options] bash
vcpkg integrate [options] zsh
vcpkg integrate [options] x-fish
Integrate vcpkg with shells and buildsystems.
Integrates with Visual Studio (Windows-only), sets the user-wide vcpkg instance, and displays CMake integration help.
On Windows with Visual Studio 2015, this subcommand will add redirecting logic into the MSBuild installation which will automatically pick up each user's user-wide vcpkg instance. Visual Studio 2017 and newer have this logic in the box.
To set the user-wide vcpkg instance, vcpkg creates a few short files containing the absolute path to the vcpkg instance inside the user's user-wide configuration location:
%LOCALAPPDATA%\vcpkg
or%APPDATA%\Local\vcpkg
on Windows$HOME/.vcpkg
or/var/.vcpkg
on non-Windows
Displays the full path to the CMake toolchain file. Running this command is not required to use the toolchain file.
Removes the user-wide vcpkg instance setting.
This command deletes the linking files from the user-wide configuration location created by vcpkg integrate install
.
Creates a linked NuGet package for MSBuild integration.
See MSBuild Per-Project Integration for more information.
Windows Only
Adds vcpkg tab-completion support to the current user's Powershell profile.
Non-Windows Only
Adds vcpkg tab-completion support to the current user's .bashrc
(.bash_profile
on MacOS).
Non-Windows Only
Adds vcpkg tab-completion support to the current user's .zshrc
.
Non-Windows Only
Adds vcpkg tab-completion support to the current user's fish shell completions directory.
$ vcpkg integrate install
Applied user-wide integration for this vcpkg root.
CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=/workspaces/vcpkg/scripts/buildsystems/vcpkg.cmake"
All vcpkg commands support a set of common options.