On Thu, 8 Jan 2015, Vittorio Giovara wrote:
On Wed, Jan 7, 2015 at 11:08 PM, Martin Storsjö <mar...@martin.st> wrote:
---
doc/general.texi | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/doc/general.texi b/doc/general.texi
index ae59941..31972ee 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -95,6 +95,14 @@ Go to @url{http://www.wavpack.com/} and follow the
instructions for
installing the library. Then pass @code{--enable-libwavpack} to configure to
enable it.
+@section OpenH264
+
+Libav can make use of the OpenH264 library for H.264 encoding.
+
+Go to @url{http://www.openh264.org/} and follow the instructions for
+installing the library. Then pass @code{--enable-libopenh264} to configure to
+enable it.
+
Sure ok, do you think it's worthwhile mentioning where to get the
cisco-blessed binary version too?
You can find that via the same page (under the FAQ).
Also, after thinking a bit more about it, using the cisco-blessed
patents-paid binary with libavcodec doesn't seem to make much sense. If a
libav user already is redistributing libavcodec, he is redistributing code
covered by patents. So if the user is afraid of this and wants to use the
cisco binary to cover it, he shouldn't be shipping libavcodec at all
(because the cisco setup only covers that particular binary, nothing
more). Or perhaps it doesn't violate the relevant patents if it is
libavcodec with all the native decoders (in particular, the H264 decoder)
disabled?
// Martin
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
