Static: such libraries will be embedded into the final FFmpeg binaries.

FFmpeg supports both, yet I used only static versions. Below I’ll give you several examples.Īn important thing to consider here is the type of library you wish to build: static or shared. The way you trigger the compilation process heavily depends on a build system chosen by library developers. You should prepare such directories as x86 for each ABI you want to support by compiling the library for each such ABI. The lib directory contains static (*.a) and/or shared (*.so) libraries. The include directory has header files that usually contains subdirectories per each specific library. It is convenient to mix several libraries in the same directory structure. Here the x86 directory is a place where both libaom and libdav1d are installed. The standard directory structure is usually made by a build system of a library for you and it looks like this: Compile the libraryįirst you need to prepare a static or a shared library and place it in a specific directory structure along with header files.

To integrate an external library into FFmpeg you need: 1. The latter is really a source of valuable information, so don’t hesitate to look inside of it. The list of libraries that can be integrated into FFmpeg can be found in the documentation or directly in the configure script. General approach to an external library integration It isn’t actually needed for the app, but its integration has some special features. Additionally I’ll integrate the libmp3lame (an MP3 encoding library). I’d like to integrate both libaom and libdav1d into FFmpeg and explain the principals of such an integration. I’m not interested in this library because it can only encode AV1. Its support currently is in master branch of FFmpeg and will be released in FFmpeg 4.3. librav1e – also a separate library that implements only an encoder of AV1 with the same claim.It is supported starting with FFmpeg 4.2 libdav1d – a separate library that implements only a decoder of AV1 and claims to be faster than libaom.It is supported starting with FFmpeg 4.0 libaom – a reference implementation of AV1 specification that supports both encoding and decoding.FFmpeg supports this codec through external libraries: AV1 codec gets more popularity and even is supported by Android 10. Just to remind you, in previous articles I created an app that decodes video frames from a video file.

Ffmpeg build with many codecs support