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
We've just been troubleshooting a linking problem in our application, were some developers receive complaints on not finding "libnghttp2.so" (among others).
We tracked it down to the fact that some developer hosts had "libnghttp2-devel" installed, which made the cpr-local build of libcurl to include them in the build, which in turn resulted in not finding the .so's during linking.
Possible Solution
Since we dont need/want to use HTTP2, it would be nice to be able to disable the usage of things like this, via a suitable CPR_SKIP_NG_HTTP2, so that set(USE_NGHTTP2 OFF) is defined when building libcurl, similarly to CPR_ENABLE_CURL_HTTP_ONLY.
Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
We've just been troubleshooting a linking problem in our application, were some developers receive complaints on not finding "libnghttp2.so" (among others).
We tracked it down to the fact that some developer hosts had "libnghttp2-devel" installed, which made the cpr-local build of libcurl to include them in the build, which in turn resulted in not finding the .so's during linking.
Possible Solution
Since we dont need/want to use HTTP2, it would be nice to be able to disable the usage of things like this, via a suitable
CPR_SKIP_NG_HTTP2
, so thatset(USE_NGHTTP2 OFF)
is defined when building libcurl, similarly to CPR_ENABLE_CURL_HTTP_ONLY.Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: