Javernaut 7f016aac6d Creating a separate script for exporting core variables		5 years ago
images	Updating README.md to display libswscale	6 years ago
scripts	Creating a separate script for exporting core variables	5 years ago
.gitignore	Printing stats about text relocations presence	5 years ago
.travis.yml	exit 1 if output binaries contain Text Relocations. This will fail the CI job.	5 years ago
README.md	Adding the link to the details of the script working to README.md	5 years ago
ffmpeg-android-maker-2.sh	Creating a separate script for exporting core variables	5 years ago
ffmpeg-android-maker.sh	Using number of cores to set the number of threads	5 years ago

README.md

ffmpeg-android-maker

Here is a script that downloads the source code of FFmpeg library and assembles it for Android. The script produces shared libraries as well as header files. The output structure looks like this:

The actual content of all this directories depends on how the FFmpeg was configured before assembling. For my purpose I enabled only libavcodec, libavformat, libavutil and libswscale, but you can set your own configuration to make the FFmpeg you need.

The version of FFmpeg here by default is 4.2.1 (but can be overridden). And the script expects to use at least Android NDK r19 (r20 also works ok).

The details of how this script is implemented are described in this blog post.

Supported Android ABIs

armeabi-v7a
arm64-v8a
x86
x86_64

Supported host OS

On macOS or Linux just execute the script in terminal.

It is also possible to execute this script on a Windows machine with MSYS2. You also need to install specific packages to it: make, git, diffutils and tar. The script supports both 32-bit and 64-bit versions of Windows.

Prerequisites

You have to define an environment variable ANDROID_NDK_HOME and set it to a correct path to your Android NDK.

See it in action

Actual Android app that uses the output of the script can be found here.

Features

Setting your own FFmpeg version. You can actually override the version of FFmpeg used by the script. See details here.

Test your script in a cloud. This repository has CI integration and you can use it too for your own configurations of FFmpeg. See details here.

Text relocations monitoring. After a build you can look into stats/text-relocations.txt file. That file lists all *.so files that were built and reports if they have text relocations. If you don't see any mentioning of 'TEXTREL' in the file, you are good. Otherwise, you will see exact binaries that have this problem.