How to build vcpkg.exe from source code? #44538
-
|
Hello! For security reasons I can not download vcpkg.exe from GitHub. How can I build it from sources? I had cloned vcpkg-tool repo, checked out 2025-03-13 tag, run commands:
And got a lot of errors. Mostly C2370, but others are present too. I can't find any instructions on how to build vcpkg.exe. How should I do it? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
We do not build with VS2019, so that is unlikely to work. In particular there have been changes to std::filesystem that we need. Our official builds are built with Ninja but there are hoops you might have to jump through first. Making this easy is kind of an explicit non-goal: the whole reason we provide binaries is to not need to constantly jump through hoops to make that easy. |
Beta Was this translation helpful? Give feedback.
-
|
You'll need to use the latest Visual Studio to build -- currently, that's VS 2022: https://visualstudio.microsoft.com/ |
Beta Was this translation helpful? Give feedback.
-
|
(To clarify: I'm not saying 'you can't build us from source', I'm saying 'you might have to jump through hoops to do that because we don't maintain explicit docs on doing so'.) |
Beta Was this translation helpful? Give feedback.
-
|
hoops:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Now I think that my problem is an old compiler version. I had tried to configure and build a project using provided commands, but still get same syntax errors. I do not believe that have const in .h and constexpr in .cpp for same entity could live in codebase if it would had compiled with errors. So, I suppose it goes to a new C++ standard syntax rules... |
Beta Was this translation helpful? Give feedback.
We do not build with VS2019, so that is unlikely to work. In particular there have been changes to std::filesystem that we need. Our official builds are built with Ninja but there are hoops you might have to jump through first.
https://github.com/microsoft/vcpkg-tool/blob/43e0cb2407ed7b85aa74a41e59e8be6b5780edb6/azure-pipelines/signing.yml#L414-L417
Making this easy is kind of an explicit non-goal: the whole reason we provide binaries is to not need to constantly jump through hoops to make that easy.