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
However, the jwt-cpp port doesn't have any such dependencies in its vcpkg.json, which breaks builds which use jwt-cpp unless the user installs an SSL library and links his final target with it.
Proposed solution
I'm not sure how vcpkg normally handles ports which allow the user to select between various different dependencies, but it would be good to have a way to automatically install the SSL libraries so that builds work out-of-the-box. Perhaps by having different jwt-cpp targets?
In the worst case scenario there could be at least a usage file explaining this.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It seems like jwt-cpp requires an SSL library to work, and supports a few different ones as indicated in its Readme: https://github.com/Thalhammer/jwt-cpp?tab=readme-ov-file#ssl-compatibility
However, the jwt-cpp port doesn't have any such dependencies in its vcpkg.json, which breaks builds which use jwt-cpp unless the user installs an SSL library and links his final target with it.
Proposed solution
I'm not sure how vcpkg normally handles ports which allow the user to select between various different dependencies, but it would be good to have a way to automatically install the SSL libraries so that builds work out-of-the-box. Perhaps by having different jwt-cpp targets?
In the worst case scenario there could be at least a usage file explaining this.
The text was updated successfully, but these errors were encountered: