Don't understand how to correctly set up vcpkg. Do I place the app in my PATH for global access, or do I bootstrap per project?

[futuremotiondev]

I am on Win11 x64 Pro, and I am following these:

• https://learn.microsoft.com/en-us/vcpkg/get_started/get-started
• https://learn.microsoft.com/en-us/vcpkg/get_started/get-started-vs
• https://learn.microsoft.com/en-us/vcpkg/get_started/get-started-msbuild
• https://learn.microsoft.com/en-us/vcpkg/get_started/get-started-vscode

My goal is to set up vcpkg globally so I can build both with CMake and MSBuild using the command line, Visual Studio, and VS Code if I want.

Basically I want to be able to use it for all scenarios it was intended for on-demand.

So I followed these steps to get vcpkg.exe spit out:

cd "O:\Repos"
git clone https://github.com/microsoft/vcpkg.git
cd vcpkg
.\bootstrap-vcpkg.bat -disableMetrics

Once I've done all this, can I now drop this whole folder into a custom directory and add it to my system %PATH% so I can use it globally?

For example:

1. Move the vcpkg folder to C:\BIN\vcpkg
2. cd to C:\BIN\vcpkg
3. Run .\vcpkg.exe integrate install (for MSBuild)
4. Open system environment variables window.
5. Create a new environment variable VCPKG_ROOT, and set it to C:\BIN\vcpkg:

6. Edit the system PATH environment variable and place %VCPKG_ROOT% at the top:

---

So, my questions:

1. Is this a viable way to set VCPKG up?
2. Will I run into conflicts if I'm building for CMake / MSBuild or can this configuration work for both?

[dg0yt]

Basically I want to be able to use it for all scenarios it was intended for on-demand.

IMO on-demand means: Don't add global environment variable settings.

Is this a viable way to set VCPKG up?

AFAIU the purpose of vcpkg integrate install is to do the right thing. Why not stop at this point?

I would not recommend to add PATH entries for locations of single executables. Adding entries to PATH has side effects, including a security perspective.

Setting VCPKG_ROOT is less concerning. It doesn't affect other programs. (And it can be overridden as needed.)

Will I run into conflicts if I'm building for CMake / MSBuild or can this configuration work for both?

I think neither cmake nor msbuild care about vcpkg being in PATH. These integrations are based on the location and content of other files. I cannot say much about setting VCPKG_ROOT globally. vcpkg shall tell you when it notices inconsistencies.