7d54e0f093
This does not do the full toolchain setup like the arm builds. It only allows for ndk-builds. See the instructions in tests/android/README or the webm jnin bindings project: https://chromium.googlesource.com/webm/bindings/+/master/JNI/README.Android Because this support is not quite polished, the build targets must be forced. Please use --force-target=x86-android-gcc --disable-ssse3 --disable-sse4_1 --disable-avx2 --force-target-mips-android-gcc Change-Id: Ie2b6623f71ac816e3965c39bf97097e9d30b6e94
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
Android.mk will build vpx unittests on android.
|
|
1) Configure libvpx from the parent directory:
|
|
./libvpx/configure --target=armv7-android-gcc --enable-external-build \
|
|
--enable-postproc --disable-install-srcs --enable-multi-res-encoding \
|
|
--enable-temporal-denoising --disable-unit-tests --disable-install-docs \
|
|
--disable-examples --disable-runtime-cpu-detect --sdk-path=$NDK
|
|
|
|
2) From the parent directory, invoke ndk-build:
|
|
NDK_PROJECT_PATH=. ndk-build APP_BUILD_SCRIPT=./libvpx/test/android/Android.mk \
|
|
APP_ABI=armeabi-v7a APP_PLATFORM=android-18 APP_OPTIM=release \
|
|
APP_STL=gnustl_static
|
|
|
|
Note: Both adb and ndk-build are available prebuilt at:
|
|
https://chromium.googlesource.com/android_tools
|
|
|
|
3) Run get_files.py to download the test files:
|
|
python get_files.py -i /path/to/test-data.sha1 -o /path/to/put/files \
|
|
-u http://downloads.webmproject.org/test_data/libvpx
|
|
|
|
4) Transfer files to device using adb. Ensure you have proper permissions for
|
|
the target
|
|
|
|
adb push /path/to/test_files /data/local/tmp
|
|
adb push /path/to/built_libs /data/local/tmp
|
|
|
|
NOTE: Built_libs defaults to parent_dir/libs/armeabi-v7a
|
|
|
|
5) Run tests:
|
|
adb shell
|
|
(on device)
|
|
cd /data/local/tmp
|
|
LD_LIBRARY_PATH=. ./vpx_test
|