This blog post summarizes changes to the vcpkg package manager as part of the 2024.09.23 and 2024.09.30 releases, 2024-09-18 and 2024-09-30 tool releases, as well as changes to vcpkg documentation throughout September. This month’s release includes some minor changes and bug fixes, 18 new ports, and 319 updates to existing ports.

When updating vcpkg, we recommend moving to the 2024.09.30 release, which fixes some regressions in the 2024.09.23 release.

Some stats for this period:

• There are now 2,491 total ports available in the vcpkg public registry. A port is a versioned recipe for building a package from source, such as a C or C++ library.
• 18 new ports were added to the open-source registry.
• 319 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.
• 45 contributors made commits (not counting the vcpkg maintainers).
• The main vcpkg repo has over 6,300 forks and 22,900 stars on GitHub.

vcpkg changelog (2024.09.23 & 2024.09.30 releases)

The following notable changes were made in September:

• Internal change: vcpkg now uses 7zip for all extractions on Windows (PRs: Microsoft/vcpkg#40416, Microsoft/vcpkg-tool#1477).
• Keep CUDA_PATH_* environment variables when forming a clean environment on Windows (PR: Microsoft/vcpkg-tool#1476, thanks @autoantwort!).
• Bug fixes:
  • Fixed a crash occurring when running the upgrade command with a port that was not already installed (PR: Microsoft/vcpkg-tool#1473, thanks @Thomas1664!).
  • Other minor bug fixes.

Documentation changes

• Added information about how to convert vcpkg-generated SPDX files to the CycloneDX format (PR: Microsoft/vcpkg-docs#403).
• Various fixes to CMake examples in Get Started tutorials, in response to user feedback (PR: Microsoft/vcpkg-docs#404).
• Other minor fixes (thanks @dg0yt and @aristotelos!).

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

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):

• Al17OTON
• AenBleidd
• aminya
• Antkmsft
• aristotelos
• autoantwort
• bc-lee
• buck-yeh
• c8ef
• ChaseKnowlden
• CrSjimo
• culhatsker
• dbolduc
• dg0yt
• GabeRundlett
• gastineau
• greg7mdp
• HappySeaFox
• Honeybunch
• hosseinmoein
• jandupej
• jiayuehua
• JoergAtGithub
• johnwason
• kadirlua
• lukasberbuer
• msclock
• miyanyan
• mostynb
• myd7349
• Neumann-A
• Olli1080
• Osyotr
• plekakis
• Rasmus-123
• rbsheth
• redbaron
• redboltz
• Shadowrom2020
• starfishmod
• SuperCodeHero
• Talregev
• Thomas1664
• waywardmonkeys
• xia-chu

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.