On Sun, 17 Jan 2016, Luca Barbato wrote:
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index e611602..196be51 100755
--- a/configure
+++ b/configure
@@ -2305,7 +2305,7 @@ ffrtmphttp_protocol_select="http_protocol"
gopher_protocol_select="network"
http_protocol_select="tcp_protocol"
httpproxy_protocol_select="tcp_protocol"
-https_protocol_select="tls_protocol"
+https_protocol_select="http_protocol tls_protocol"
icecast_protocol_select="http_protocol"
librtmp_protocol_deps="librtmp"
librtmpe_protocol_deps="librtmp"
--
2.6.1
Why? In libavformat/Makefile, both protocols list the same object files,
and topologically, the https protocol implementation never calls the http
protocol implementation (i.e., it never uses the ff_http_protocol struct
or internally opens a http:// url).
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
