How to build ffmpeg with hardware accelerated codecs for Android x86
In order to build a complete ffmpeg with hardware acceleration for Intel platform (XXX lake + Atom), we need a complete Android x86 build, the cross-compilation doesn't work well with NDK or anything else.
Steps are below.
Install Ubuntu 16.04 LTS x86-64, install the all Ubuntu dependencies as here.
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev libxml2-utils xsltproc unzip
Install Python Mako by pip, which the build system uses to generate the i18n files during compilation.
sudo apt-get install python-pip pip install mako
Get the source code of Android x86, here make sure you have large enough space.
mkdir android-x86
cd android-x86
repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b $branch
repo sync --no-tags --no-clone-bundle
The variable $branch is the name of specific Android branch.
- oreo-x86
- Android 8.0
- nougat-x86
- Android 7.1
- marshmallow-x86
- Android 6.0
- lollipop-x86
- Android 5.1
- kitkat-x86
- Android 4.4
- jb-x86
- Android 4.3
- ics-x86
- Android 4.0
- honeycomb-x86
- Android 3.2
- gingerbread-x86
- Android 2.3
- froyo-x86
- Android 2.2
- eclair-x86
- Android 2.1
- donut-x86
- Android 1.6
- cupcake-x86 (aka android-x86-v0.9)
- Android 1.5
Once the code base was checked out, use lunch command to build the system for once.
Enter the folder of checked out folder.
Source the build environement setup.
. build/envsetup.sh
Select the build target and type of build
lunch $TARGET_PRODUCT-$TARGET_BUILD_VARIANT
The $TARGET_PRODUCT could be one of android_x86 android_x86_64 .
The $TARGET_BUILD_VARIANT could be one of eng user userdebug .
So if we want to make a debug version of Android x86-64, we type
lunch android_x86_64-userdebug
Now type
m -jX iso_img
to make the system image.
When there is the error about org.android.analytics, open the file
./build/core/tasks/check_boot_jars/package_whitelist.txt
and append a line
org\.android_x86\.analytics
to it.
If everything goes okay, the Android system image would be build.
Now we start to build a better ffmpeg with hardware acceleration API, vaapi, cuvid etc. The system already offer the possibilty but didn't supply the correct configuration as the default.
Copy the file
external/ffmpeg/libavformat/Android.mk
to
external/ffmpeg/libavfilter
If you want to build the command line of ffmpeg, create a new Android.mk file under external/tools folder, fill it with content
LOCAL_PATH:= $(call my-dir) include $(CLEAR_VARS) LOCAL_CFLAGS += \
-DANDROID \
-DTARGET_CONFIG=\"config-x86_64-x86_64.h\" \ LOCAL_SRC_FILES := \
../ffmpeg.c \
../ffmpeg_filter.c \
../ffmpeg_opt.c \
../ffmpeg_cuvid.c \
../ffmpeg_vaapi.c \
../cmdutils.c \ LOCAL_C_INCLUDES += \
$(LOCAL_PATH)/android/include \
$(LOCAL_PATH)/.. \ LOCAL_SHARED_LIBRARIES := libavutil libavcodec libswscale libswresample libswscale libavformat libavfilter LOCAL_MODULE_TAGS := optional
LOCAL_MODULE := ffmpeg include $(BUILD_EXECUTABLE)
Then that's it, you would have the ffmpeg command line under /system/bin/ffmpeg !
Do not touch the script gen-android-configs and configure with ffmpeg.
Now let's add more dependency to the system, such as libva-utils for the Intel platform to detect the video codec capability of the system.
Under the folder external, clone the repository at branch 1.8.3
git clone -b 1.8. https://github.com/intel/libva-utils.git
Enter the libva-utils folder, change a bit the source code. The system's libva under driver is 1.1.0, it's not very compatible with the libva-utils, which is a new program.
diff --git a/vainfo/vainfo.c b/vainfo/vainfo.c
index ..5d9f055
--- a/vainfo/vainfo.c
+++ b/vainfo/vainfo.c
@@ -, +, @@ int main(int argc, const char* argv[])
const char *name = strrchr(argv[], '/');
VAProfile profile, *profile_list = NULL;
int num_profiles, max_num_profiles, i;
- VAEntrypoint entrypoint, entrypoints[];
+ VAEntrypoint entrypoints[];
+ int entrypoint_index;
int num_entrypoint;
int ret_val = ; @@ -, +, @@ int main(int argc, const char* argv[])
va_status = vaInitialize(va_dpy, &major_version, &minor_version);
CHECK_VASTATUS(va_status, "vaInitialize", ); - printf("%s: VA-API version: %d.%d (libva %s)\n",
- name, major_version, minor_version, LIBVA_VERSION_S);
+ printf("%s: VA-API version: %d.%d\n",
+ name, major_version, minor_version); driver = vaQueryVendorString(va_dpy);
printf("%s: Driver version: %s\n", name, driver ? driver : "<unknown>");
@@ -, +, @@ int main(int argc, const char* argv[])
CHECK_VASTATUS(va_status, "vaQueryConfigEntrypoints", ); profile_str = profile_string(profile);
- for (entrypoint = ; entrypoint < num_entrypoint; entrypoint++)
- printf(" %-32s: %s\n", profile_str, entrypoint_string(entrypoints[entrypoint]));
+ for (entrypoint_index = ; entrypoint_index < num_entrypoint; entrypoint_index++)
+ printf(" %-32s: %s\n", profile_str, entrypoint_string(entrypoints[entrypoint_index]));
Just make the vainfo.c is able to be compiled with system libva.
Back to the folder android-x86, type
mmm external/libva-utils
to just build the specific module. That's it, now the /system/bin/vainfo would be there !
References
- http://www.android-x86.org/getsourcecode
- https://github.com/CyanogenMod/android_external_ffmpeg
- https://github.com/intel/libva
- https://github.com/intel/libva-utils
How to build ffmpeg with hardware accelerated codecs for Android x86的更多相关文章
- How to Build FFmpeg for Android
http://www.roman10.net/how-to-build-ffmpeg-for-android/ ffmpeg is an open-source platform for record ...
- 硬件加速 Hardware Accelerated 绘制
官方文档中对硬件加速的描述 原文地址:http://developer.android.com/guide/topics/graphics/hardware-accel.html Beginning ...
- Build FFmpeg for iOS
FFmpeg Build Instructions MAC 10.8 or better Copy ffmpeg-2.0.tar.bz2 (https://ffmpeg.org/releases/ff ...
- CSS开启硬件加速 hardware accelerated
作者:孙志勇 微博 日期:2016年12月6日 一.时效性 所有信息都具有时效性.文章的价值,往往跟时间有很大关联.特别是技术类文章,请注意本文创建时间,如果本文过于久远,请读者酌情考量,莫要浪费时间 ...
- VS 的编译选项 build下的 platform target -- Any CPU和x86有什么影响?
VS 的编译选项 build下的platform -- Any CPU和x86有什么影响? 现在的问题是,我的一个assembly用Any CPU编译就不能在64位系统下运行了,但是用x86编译就ok ...
- Using Qt to build an Omi App for iOS (and Android)
JUNE 6, 2014 / HHARTZ Working on projects where the technology is pre-determined, it's often difficu ...
- ffmpeg学习笔记-Linux下编译Android动态库
Android平台要使用ffmpeg就需要编译生成动态库,这里采用Ubuntu编译Android动态库 文件准备 要编译生成Android需要以下文件 NDK ffmpeg源代码 NDK下载 NDK可 ...
- 最简单的基于FFmpeg的移动端例子:Android 视频转码器
http://blog.csdn.net/leixiaohua1020/article/details/47056365
- (转载)中文Appium API 文档
该文档是Testerhome官方翻译的源地址:https://github.com/appium/appium/tree/master/docs/cn官方网站上的:http://appium.io/s ...
随机推荐
- 关于overfit的随笔
看到@ 爱可可-爱生活转发的文章.稍微看了下,在这里记录下. overfit是机器学习的一个重要概念.在狭义上可以定义为模型过于复杂,导致模型的generalization不够好.我认为应采用一个更广 ...
- 微信小程序开发资源汇总 💯
目录 官方文档 工具 插件 讨论 教程 视频教程 文章 代码 轮子 置顶 WePY:组件化的小程序开发框架
- idea快捷
IntelliJ Idea 常用快捷键 列表(实战终极总结!!!!) 1. -----------自动代码-------- 常用的有fori/sout/psvm+Tab即可生成循环.System.ou ...
- 集成学习之Boosting —— AdaBoost原理
集成学习大致可分为两大类:Bagging和Boosting.Bagging一般使用强学习器,其个体学习器之间不存在强依赖关系,容易并行.Boosting则使用弱分类器,其个体学习器之间存在强依赖关系, ...
- js术语扫盲贴:XHR、RegExp、call-apply、prototype
(1) XHR:xml httprequestXHR注入:XHR 注入技术是通过XMLHttpRest来获取javascript的.但与eval不同的是,该机制是通过创建一个script的DOM元素, ...
- java.exe进程来源排查录
解决后的一个小结:此处是一个tomcat端口,这种情况下,可以先在浏览器访问下看看效果,就可以快速定位 又发现一个简单的办法: 下面的定位过程,适用于各种场合 无意中发现有个进程开了好多端口,很奇怪 ...
- salesforce lightning零基础学习(四) 事件(component events)简单介绍
lightning component基于事件驱动模型来处理用户界面的交互.这种事件驱动模型和js的事件驱动模型也很相似,可以简单的理解成四部分: 1.事件源:产生事件的地方,可以是页面中的输入框,按 ...
- LoadRunner 11 中Analysis分析
原文:http://www.cnblogs.com/Chilam007/p/6445165.html analysis简介 分析器就是对测试结果数据进行分析的组件,它是LR三大组件之一,保存着大量用来 ...
- jQuery学习之旅 Item5 $与jQuery对象
1.$符号的由来 $符号本质就是函数的名字. jquery源码分析 通过分析我们知道,在jquery里边不只可以使用$符号,还可以使用jQuery标志 解决冲突问题 有的项目是中间过渡项目(proto ...
- Java 学习笔记 (五) Java Compile\Build\Make的区别
以下内容引自: http://blog.51cto.com/lavasoft/436216 Compile.Make和Build的区别 原创leizhimin2010-11-30 11:30:20评论 ...