Skip to content

cmake: Multiple SSL backends causes build failure in combination with optional protocols #18246

@diizzyy

Description

@diizzyy

I did this

I'm not entirely sure how this is supposed to work but looking at both CMake and Autotools utilizing multiple SSL backends are supported. However if you enable HTTP3 support for example at least with CMake this possibly unintentionally breaks the build.

Lets say you have OpenSSL 3.0 which doesn't support QUIC but you also have fairly recent version of GnuTLS such as 3.8.10

Now if you enable HTTP3 support using (lib)ngtcp2, and both OpenSSL and GnuTLS it'll set OpenSSL support as required which fails as it's older than 3.5. The only way to get around this is to disable OpenSSL alltogether, not sure if that's the intention?

I expected the following

No response

curl/libcurl version

curl 8.15.0 (release)

operating system

FreeBSD 14.3-RELEASE

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions