Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I know which .so files to keep in Android? #21

Closed
jaccunio opened this issue Aug 13, 2014 · 1 comment
Closed

How can I know which .so files to keep in Android? #21

jaccunio opened this issue Aug 13, 2014 · 1 comment
Labels

Comments

@jaccunio
Copy link

Hi, I'm very pleased with this library, it saved me lots of time by not having to deal with ffmpeg directly in Android.
One thing that worries me is the size of resulting /libs/armeabi folder - I followed the instructions in the readme and right now it's almost 36MB (which is a lot for an Android app)
As I'm using only a two javacv's classes in my code (FFmpegFrameRecorder and opencv_core.IplImage) I'm pretty sure I could ditch most of the .so files - how can I find out which ones?

@jaccunio jaccunio changed the title How do I know which .so files to keep in Android? How can I know which .so files to keep in Android? Aug 13, 2014
@saudet
Copy link
Member

saudet commented Aug 17, 2014

The only sure way is to remove the .so files one by one, and when your application fails, you know that that file was needed. If it still runs, then you don't need that file and can keep it removed.

BTW, if we modify FFmpegFrameRecorder to not use IplImage (it's not required for anything really), we can also remove opencv_core.so, which is pretty big.

If you need to make it smaller still, you'll need to modify the cppbuild.sh scripts and remove all the features you don't need from FFmpeg, and rebuild the .so files themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants