[curl] Default features not getting disabled, using a specific SSL backend is basically impossible #32838
Labels
category:port-bug
The issue is with a library, which is something the port should already support
Is your feature request related to a problem? Please describe.
When in manifest mode, default features cannot be disabled. Having this as a dependency in my vcpkg.json:
{ "name": "curl", "default-features": false },
I see that curl is getting build with the default options still enabled:
curl[core,non-http,sectransp,ssl]
. This makes it impossible to build only for http usage, and to select a custom SSL backend.Furthermore, the http2 option also forces the default ssl backend, which again, makes it impossible to use a specific backend exclusively.
Proposed solution
The expected behaviour would be that the default-features switch works, and the http2 option shouldn't depend on the default ssl backend feature, when a custom ssl backend is enabled.
Describe alternatives you've considered
No response
Additional context
Building with options:
"mbedtls", "http2", "brotli", "zstd", "tool"
, output ofcurl -V
Actual:
Expected (with modified vcpkg.json for the port):
The text was updated successfully, but these errors were encountered: