This blog post summarizes changes to the vcpkg package manager as part of the 2024.12.16 registry release, 2024-12-09 tool release, as well as changes to vcpkg documentation throughout December. This release includes a command line option to force vcpkg to use classic mode even if a manifest file is found along with bug fixes.
Some stats for this period:
- There are now 2,516 total ports available in the vcpkg curated registry. A port is a versioned recipe for building a package from source, such as a C or C++ library.
- 12 new ports were added to the curated registry.
- 309 updates were made to existing ports. As always, we validate each change to a port by building all other ports that depend on or are depended by the library that is being updated for our 13 main triplets.
- 27 contributors made commits (not counting the vcpkg maintainers).
- The main vcpkg repo has over 6,500 forks and 23,500 stars on GitHub.
vcpkg changelog (2024.12.16 release)
The following notable changes were made in December:
- Fixed several bugs with the SPDX generation feature (PR: Microsoft/vcpkg-tool#1377, thanks @Thomas1664!).
- Use GITHUB_SERVER_URL to change GitHub API host for dependency graph submission (PR: Microsoft/vcpkg-tool#1547, thanks @luncliff!).
- Other minor bug fixes.
Documentation changes
- New article: Set up caching using Azure Storage and Azure DevOps. Documents how to use Workload Identity Federation to configure binary and asset caching with Azure Storage containers and vcpkg. This is a mechanism where Azure DevOps takes care of secrets rotation and management for you that can be used with vcpkg. (PR: Microsoft/vcpkg-docs#423).
If you have any suggestions for our documentation, please submit an issue in our GitHub repo or see the box at the bottom of a particular article.
Total ports available for tested triplets
triplet | ports available |
x64-windows | 2,403 |
x86-windows | 2,297 |
x64-windows-static | 2,276 |
x64-windows-static-md | 2,323 |
arm64-windows | 2,006 |
arm64-windows-static-md | 1,987 |
x64-uwp | 1,319 |
arm64-uwp | 1,295 |
x64-linux | 2,376 |
x64-osx | 2,250 |
arm64-osx | 2,173 |
arm-neon-android | 1,665 |
x64-android | 1,743 |
arm64-android | 1,710 |
While vcpkg supports a much larger variety of target platforms and architectures (as community triplets), the list above is validated exhaustively to ensure updated ports don’t break other ports in the catalog.
Thank you to our contributors
vcpkg couldn’t be where it is today without contributions from our open-source community. Thank you for your continued support! The following people contributed to the vcpkg, vcpkg-tool, or vcpkg-docs repos in this release (listed alphabetically by GitHub username):
- AenBleidd
- alanxz
- an-tao
- autoantwort
- buracchi
- c8ef
- deniskovalchuk
- dg0yt
- donny-dont
- erikyuzwa
- gwankyun
- jeremy-rifkin
- JoergAtGithub
- karastojko
- kp-cat
- lukasberbuer
- luncliff
- miyanyan
- mohit1234
- Neumann-A
- nlogozzo
- robojan
- talregev
- tandresen77
- ThijsWithaar
- Thomas1664
- tomconder
- Tradias
- wolfgitpr
Learn more
You can find the main release notes on GitHub. Recent updates to the vcpkg tool can be viewed on the vcpkg-tool Releases page. To contribute to vcpkg documentation, visit the vcpkg-docs repo. If you’re new to vcpkg or curious about how a package manager can make your life easier as a C/C++ developer, check out the vcpkg website – vcpkg.io.
If you would like to contribute to vcpkg and its library catalog, or want to give us feedback on anything, check out our GitHub repo. Please report bugs or request updates to ports in our issue tracker or join more general discussion in our discussion forum.
0 comments
Be the first to start the discussion.