You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
馃搵 Description Vcpkg is a rising C++ Library Manager for Windows, Linux, and MacOS, which is developed by Microsoft.
We want to have a vcpkg package badge to show our project can be found in vcpkg library manager, such as "vcpkg | v1.0.0" or other similiar format.
馃敆 Data
Package data can be found in the repo of vcpkg itself.
Information of all package are stored in the directory ports/.
For example, you can find info of package protopuf in ports/protopuf/vcpkg.json.
No API key is required.
馃帳 Motivation
Vcpkg is becoming more and more popular.
I hope to have a badge after releasing my library, and I think other library developers also have this demand.
And because it is very simple to obtain library information, I think it may not be difficult to implement.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion, this sounds reasonable. I would expect the implementation to end up looking quite similar to our existing Scoop service, but simpler given that retrieving a separate list of buckets won't be needed here.
馃搵 Description
Vcpkg is a rising C++ Library Manager for Windows, Linux, and MacOS, which is developed by Microsoft.
We want to have a vcpkg package badge to show our project can be found in vcpkg library manager, such as "vcpkg | v1.0.0" or other similiar format.
馃敆 Data
Package data can be found in the repo of vcpkg itself.
Information of all package are stored in the directory
ports/
.For example, you can find info of package
protopuf
inports/protopuf/vcpkg.json
.No API key is required.
馃帳 Motivation
Vcpkg is becoming more and more popular.
I hope to have a badge after releasing my library, and I think other library developers also have this demand.
And because it is very simple to obtain library information, I think it may not be difficult to implement.
The text was updated successfully, but these errors were encountered: