Pre-build .aar issue

[HBiSoft]

I'm not sure if this library is still supported, there was no activity by the owner @wseemann in almost a year.

I hope that someone can please provide me with a explanation on how to use the .aar files to build different apk's based on their ABI. I could not find any documentation or example on how to split the apk with different .aar files. I have seen issues on the library where the owner mentioned that the pre-build .aar's should be used to reduce the apk size, but no explanation on how to actually use it.

Also, the way the pre-builld .aar are named are confusing:

I assume the following, please correct me if I'm wrong:

• aal-fmmr.aar = All ABI's
• arm_64-fmmr.aar = arm64-v8a
• arm-fmmr.aar = armeabi
• armv7-fmmr.aar = armeabi-v7a
• mips-fmmr.aar = mips
• x86_64-fmmr.aar = x86_64
• x86-fmmr.aar = x86

I also posted a question on stackoverflow - https://stackoverflow.com/questions/52253127/generate-apk-for-different-architectures-ffmpegmediametadataretriever

[wseemann]

I'm unclear why you think the prebuilt AAR names to be confusing when you were able to reconcile each ABI architecture based off my naming convention. Regardless, you can generate different APK's using product flavors which specify the desired target ABI. You can then specify which FMMR gradle dependency or standalone AAR file to use depending on each product flavor. See the attached build.gradle file for reference.

build.gradle

[HBiSoft]

Thank you for answering and the great explanation on SO. I will be closing this issue.