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
Without these frameworks compiled in, the --with-rustls flag on Macs fails with a bunch of errors related to missing symbols that are present in the CoreFoundation or Security frameworks.
People may not notice this because compilation does not error if you include the --with-secure-transport flag - that one appends the correct CoreFoundation framework flags to LDFLAGS. Unfortunately including that flag means that curl chooses SecureTransport for TLS and not rustls, so as is, it's essentially impossible to use rustls for TLS on Mac.
The text was updated successfully, but these errors were encountered:
Previously compiling rustls on Mac would only complete if you also
compiled the SecureTransport TLS backend, which curl would prefer to
the Rust backend.
Appending these flags to LDFLAGS makes it possible to compile the
Rustls backend on Mac without the SecureTransport backend, which means
this patch will make it possible for Mac users to use the Rustls
backend for TLS.
Fixescurl#6955.
Without these frameworks compiled in, the
--with-rustls
flag on Macs fails with a bunch of errors related to missing symbols that are present in the CoreFoundation or Security frameworks.People may not notice this because compilation does not error if you include the
--with-secure-transport
flag - that one appends the correct CoreFoundation framework flags to LDFLAGS. Unfortunately including that flag means that curl chooses SecureTransport for TLS and not rustls, so as is, it's essentially impossible to use rustls for TLS on Mac.The text was updated successfully, but these errors were encountered: