HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
vcpkg
CMake2016–2024
microsoft / vcpkg

vcpkg

C++ Library Manager for Windows, Linux, and MacOS

28Distinct people
34Mentions
0Explicit recommenders
27.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

C++ Library Manager for Windows, Linux, and MacOS

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year34 dated mentions

Observed mentions: 2016-09-30 12:46:27 UTC to 2024-11-03 00:03:26 UTC.

02462016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC312
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC725
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC615
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC505

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
🌐 Read in a different language vcpkg overview vcpkg is a free and open-source C/C++ package manager maintained by Microsoft and the C++ community. Initially launched in 2016 as a tool for assisting developers in migrating their projects to newer versions of Visual Studio, vcpkg has evolved into a cross-platform tool used by developers on Windows, macOS, and Linux. vcpkg has a large collection of open-source libraries and enterprise-ready features designed to facilitate your development process with support for any build and project systems. vcpkg is a C++ tool at heart and is written in C++ with scripts in CMake. It is designed from the ground up to address the unique pain points C/C++ developers experience. This tool and ecosystem are constantly evolving, and we always appreciate contributions! Learn how to start contributing with our packaging tutorial and maintainer guide. Get started First, follow one of our quick start guides. Whether you're using CMake, MSBuild, or any other build system, vcpkg has you covered: vcpkg with CMake vcpkg with MSBuild vcpkg with other build systems You can also use any editor: vcpkg with Visual Studio vcpkg with Visual Studio Code vcpkg with CLion vcpkg with Qt Creator If a library you need is not present in the vcpkg registry, open an issue on the GitHub repository or contribute the package yourself. After you've gotten vcpkg installed and working, you may wish to add tab completion to your terminal. Use vcpkg Create a manifest for your project's dependencies: vcpkg new --application vcpkg add port fmt Or install packages through the command line: vcpkg install fmt Then use one of our available integrations for CMake, MSBuild or other build systems. For a short description of all available commands, run vcpkg help. Run vcpkg help [topic] for details on a specific topic. Key features vcpkg offers powerful features for your package management needs: easily integrate with your build system control the versions of your dependencies package and publish your own packages reuse your binary artifacts enable offline scenarios with asset caching Contribute vcpkg is an open source project, and is thus built with your contributions. Here are some ways you can contribute: Submit issues in vcpkg or existing packages Submit fixes and new packages Please refer to our maintainer guide and packaging tutorial for more details. This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or email opencode@microsoft.com with any additional questions or comments. Resources Ports: Microsoft/vcpkg Source code: Microsoft/vcpkg-tool Docs: Microsoft Learn | vcpkg Website: vcpkg.io Email: vcpkg@microsoft.com Discord: #include <C++>'s Discord server, in the #🌏vcpkg channel Slack: C++ Alliance's Slack server, in the #vcpkg channel License The code in this repository is licensed under the MIT License. The libraries provided by ports are licensed under the terms of their original authors. Where available, vcpkg places the associated license(s) in the location installed/<triplet>/share/<port>/copyright. Security Most ports in vcpkg build the libraries in question using the original build system preferred by the original developers of those libraries, and download source code and build tools from their official distribution locations. For use behind a firewall, the specific access needed will depend on which ports are being installed. If you must install it in an "air gapped" environment, consider installing once in a non-"air gapped" environment, populating an asset cache shared with the otherwise "air gapped" environment. Telemetry vcpkg collects usage data in order to help us improve your experience. The data collected by Microsoft is anonymous. You can opt-out of telemetry by: running the bootstrap-vcpkg script with -disableMetrics passing --disable-metrics to vcpkg on the command line setting the VCPKG_DISABLE_METRICS environment variable Read more about vcpkg telemetry at https://learn.microsoft.com/vcpkg/about/privacy.
Read the full README on GitHub

What Hacker News says

34 sources
re: C/C++ development: anybody using conda/pixi for dependency management? Here's an example of compiling a C++ SDL program using pixi and the SDL dependency from conda-forge [1]. Seems viable as a replacement for things like vckpg [2] which only builds from source. I'm still researching this but it seems like rattler [3] is the tool to use to build/publish packages. The supported repos are: prefix.dev's own hosting, anaconda.org, artifactory or a self-hosted server. -- 1: https://github.com/prefix-dev/pixi/blob/main/examples/cpp-sd... 2: https://github.com/microsoft/vcpkg 3: https://prefix-dev.github.io/rattler-build/latest/authentica...
In Xmake: A cross-platform build utility based on Lua
The fact that Buck2 is written in a statically-compilable language is compelling, compared to Bazel and others. It's also great that Windows appears to be supported out of the box [1,1a] -- and even tested in CI. I'm curious how much "real world" usage it's gotten on Windows, if any. I don't see many details about the sandboxing/hermetic build story in the docs, and in particular whether it is supported at all on Linux or Windows (the only mention in the docs is Darwin). It's a good sign that the Conan integration PR [2] was warmly received (if not merged, yet). I would hope that the system is extensible enough to allow hooking in other dependency managers like vcpkg. Using an external PM loses some of the benefits, but it also dramatically reduces the level of effort for initial adoption. I think bazel suffered from the early difficultie
Read the rest
s integrating with other systems, although IIUC rules_foreign_cc is much better now. If I'm following the code/examples correctly, Buck2 supports C++ out of the box, but I can't quite tell if/how it would integrate with CMake or others in the way that rules_foreign_cc does. (one of the major drawbacks of vcpkg is that it can't do parallel dependency builds [3]. If Buck2 was able to consume a vcpkg dependency tree and build it in parallel, that would be a very attractive prospect -- wishcasting here) [1] https://buck2.build/docs/developers/windows_cheat_sheet/ [1a] https://github.com/facebook/buck2/blob/738cc398ccb9768567288... [2] https://github.com/facebook/buck2/pull/58 [3] https://github.com/microsoft/vcpkg/discussions/19129
In Buck2: Our open source build system
vcpkg [1] is also a workable C package manager. It mainly has C++ packages but does include a few C packages e.g. glib [2]. In addition, you can use it on a separate list of package recipes (portfiles as vcpkg calls them), in case you want to use packages not in the central repo. It's based on CMake and runs on Windows and Linux (and other platforms I think but I haven't tried). [1] https://vcpkg.io/ [2] https://github.com/microsoft/vcpkg/tree/master/ports/glib
In C Package Manager
> "it does generate something compatible with VST2.x and I've been working on VST3 this week-end (and pulling a few hairs, that API is horrendous, the smallest example is a few thousand lines of codes)." Oh that is awesome!!! If you want a tip about the smallest possible VST3 implementation, (and maybe you already know this) there is a class called "SingleComponentEffect", and an example called "AGainSimple" that uses it and is a fully self-contained single file full VST3 plugin: https://github.com/steinbergmedia/vst3_public_sdk/search?q=s... Also, I spent some time trying to get VST3 SDK usable with vcpkg so you could just do: // vcpkg.json { "name": "my-audio-lib", "dependencies": [ { "name": "vst3sdk", "version>=": "3.7.3" } ] } And your CMake would just install it for you: https://github
Read the rest
.com/microsoft/vcpkg/issues/5660#issuecomment-... It ended up requiring more changes than this, but in the end I wound up fixing the CMake build so it spit out both the VST3 SDK (helper classes) shared lib and the almost-header-only lib ("pluginterfaces" directory). I ought to upload the patches somewhere in case it's useful for you/anyone else. > "yes, that's a goal, make your DSP processor in C++ and then write a small UI for it in python or QML without having to write binding code." That would be incredible! I think the industry focus on doing UI in C++ is a bit nutty, as an outsider (but what do I know). > "- asm("...") only wants string literals, strings generated through constexpr don't cut it (otherwise it'd be possible and even relatively easy to generate e.g." Waaay over my head!!
In Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins

Showing the 15 most recent of 34 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.