mirror of https://github.com/androidx/media.git synced 2025-04-30 06:46:50 +08:00

History

tonihei edbc2046e2 Clean-up manifest merge attributes.

1. Remove tools:replace in manifest files. This attribute is only needed to establish priority when two manifests are merged and have the same attribute with different values.
As this is not happening here, the attributes can be removed.

2. Some BUILD files also define a deprecated manifest merge strategy different from the android default merge strategy. For consistency these are set to "android'.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=158075128

2017-06-06 16:38:45 +01:00

src

Clean-up manifest merge attributes.

2017-06-06 16:38:45 +01:00

build.gradle

Generate combined Javadoc

2017-03-22 19:11:28 +00:00

proguard-rules.txt

Fix gradle/proguard setup

2017-01-13 17:27:25 +00:00

README.md

vp9_extension: Update libyuv build configuration

2017-04-26 15:12:51 +01:00

README.md

ExoPlayer VP9 Extension

Description

The VP9 Extension is a Renderer implementation that helps you bundle libvpx (the VP9 decoding library) into your app and use it along with ExoPlayer to play VP9 video on Android devices.

Build Instructions

Checkout ExoPlayer along with Extensions:

git clone https://github.com/google/ExoPlayer.git

Set the following environment variables:

cd "<path to exoplayer checkout>"
EXOPLAYER_ROOT="$(pwd)"
VP9_EXT_PATH="${EXOPLAYER_ROOT}/extensions/vp9/src/main"

Download the Android NDK and set its location in an environment variable:

NDK_PATH="<path to Android NDK>"

Fetch libvpx and libyuv:

cd "${VP9_EXT_PATH}/jni" && \
git clone https://chromium.googlesource.com/webm/libvpx libvpx && \
git clone https://chromium.googlesource.com/libyuv/libyuv libyuv

Checkout the appropriate branches of libvpx and libyuv (the scripts and makefiles bundled in this repo are known to work only at these versions of the libraries - we will update this periodically as newer versions of libvpx/libyuv are released):

cd "${VP9_EXT_PATH}/jni/libvpx" && \
git checkout tags/v1.6.1 -b v1.6.1 && \
cd "${VP9_EXT_PATH}/jni/libyuv" && \
git checkout 996a2bbd

Run a script that generates necessary configuration files for libvpx:

cd ${VP9_EXT_PATH}/jni && \
./generate_libvpx_android_configs.sh "${NDK_PATH}"

Build the JNI native libraries from the command line:

cd "${VP9_EXT_PATH}"/jni && \
${NDK_PATH}/ndk-build APP_ABI=all -j4

In your project, you can add a dependency to the VP9 Extension by using a the following rule:

// in settings.gradle
include ':..:ExoPlayer:library'
include ':..:ExoPlayer:extension-vp9'

// in build.gradle
dependencies {
    compile project(':..:ExoPlayer:library')
    compile project(':..:ExoPlayer:extension-vp9')
}

Now, when you build your app, the VP9 extension will be built and the native libraries will be packaged along with the APK.

Notes

Every time there is a change to the libvpx checkout:
- Android config scripts should be re-generated by running generate_libvpx_android_configs.sh
- Clean and re-build the project.
If you want to use your own version of libvpx or libyuv, place it in ${VP9_EXT_PATH}/jni/libvpx or ${VP9_EXT_PATH}/jni/libyuv respectively. But please note that generate_libvpx_android_configs.sh and the makefiles need to be modified to work with arbitrary versions of libvpx and libyuv.