Keep yourself up to date with all new features and changes made to the platform.
The platform has been updated to support a new feature data structure introduced in microsoft/vcpkg-tool#813.
This new Vcpkg feature enables port maintainers to indicate when a feature or a default feature should be included, based on the targeted triplet.
For a practical illustration of this new syntax, refer to the
cpprestsdk port.
Besides the support of GitHub, GitLab, Bitbucket and SourceForge are now detected and displayed in each port pages.
The information can also be queried through the search with the repository
special filter:
It seems that a common pattern is to add an alternative as a depdency for deprecated ports. Therefore, this dependency is now highlighted in the warning displayed on each deprecated ports.
Some examples can be found in the following deprecated ports:
As a beta feature, these ports can also be found directly through the search
with the filter deprecated. For example,
deprecated:true provides a list of all ports that
are considered deprecated.
After the contribution to badges/shields#8923, it seemed useful for potential integrations to expose the data collected by the platform from Vcpkg public repository and other sources. This information can now be accessed as a JSON file under the following pattern.
https://vcpkg.link/ports/{portName}.json
The exposed data is only updated daily with the rest of the platform.
Thanks to the vcpkg_from_github function call available in the
portfile.cmake of ports, it is possible to extract the GitHub repository that
some ports are fetching information from.
The search functionality had a drastic search speed improvement and should now react almost instantly. Before this release, the initial load of the search page could take up to 4 seconds.
Since each port have a
support expression
describing what platform is supported by a given port, an overview has been
added to the home page for each official triplets. These official triplets are
available on the
triplets folder and
excludes the community triplets.
The number differs from vcpkg releases since it excludes some failing integration tests. Therefore, the overview available is only a theorical value.
Since the focus of the platform is to bring visibility to ports' features, they have been added to the search functionality. You can try it out with one of the following examples.
As one of the most requested features, this release provides access to the publication date of each port's version.
Thanks to this data, different pages to browse available ports have also been added.
Since it is not always possible or easy to upgrade to the latest version of a port, a new view has been added to see the version history. It includes also which features are available.
This initial release focuses on bringing visibility to available ports' features.