[FFmpeg-devel] RFC: opinions on making fftools work like a library

[Steven Liu]

Zhao Zhili <quinkblack at foxmail.com> 于2023年3月3日周五 18:15写道：
>
> I'd like to know what do you think about making fftools work like a
> library, like what ffmpeg-kit already did, but with built-in support.
>
> https://github.com/arthenica/ffmpeg-kit
>
>    FFmpegKit is a collection of tools to use FFmpeg in Android, iOS,
>    Linux, macOS, tvOS, Flutter and React Native applications.
>
>    It includes scripts to build FFmpeg native libraries, a wrapper
>    library to run FFmpeg/FFprobe commands in applications and 8
>    prebuilt binary packages available at Github, Maven Central,
>    CocoaPods, pub and npm.
>
> Pro:
> 1. It can be used for testing on mobile devices.
> 2. It can be used directly to do useful work.
> 3. It can combine some work from projects like ffmpeg-kit to extend the
> funtion.
>
> Cons:
> 1. It makes things complicated.
> 2. It's hard to support mobile devices.
>
> Welcome to comments. I want to know is it:
>
> a. Absolutely no! It's not fftools supported to do.
> b. Doesn't matter/Don't care.
> c. I like the idea, (but...)

I think there have two problem when testing on mobile devices for me:
1. The ABI of libav* always be modified.
2. There have lots of error when i run fate on mobile devices

1.  just make a portable framework between ffmpeg and downstream
modules, eg. video editor, live streaming publisher.
If ffmpeg modified the ABI, just modify the framework should be ok.
But this should not part of ffmpeg.

2. I don't get lots of time to fix them. And not sure if you have same problem.

>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".


Thanks
Steven