Issue
I used the GDAL Library in my application and it has been working properly. The Google play service announced that they upload only 64-bit compliant APK after 1st Aug 2019. So I rendered the project to 64 bit compliant. Unfortunately, there has some issue happened in GDAL library. they showing that no implementation for the gdal library(ie the .so file according to the ABI type). So I think the corresponding GDAL 64 bit were unavailable for this scope. I have the .so file in armeabi folder which is 32 bit compliant. Then I switched to arm64-V8a compliant. After that I generate the build, the corresponding .so file is not there in arm64-v8a folder. So my question is, How we can generate the 64 bit .so files from GDAL Library? Note: Normally I used 32 bit compliant APK and it has been running properly. According to the new requirement of Playstore I used 64-bit compliant APK and done a smoke testing,unfortunately they get crashed, the issue of this crash is that, I used a GDAL library,which has a .so files with respect to ABI type. so when I run in 64 bit, the error showing that no implementation found for GDAL. Hence I used the apk analyzer to look the difference from 32 bit compliant. so I identified that there is no .so file related to arm64-V8a folder. So I think we need to generate the 64 bit .so file for the GDAL Library. Is there any solution to generate this I here by adding the screen shots, see the lib folder 32 bit compliant 64bit compliant 3`.so files inside armeabi
Solution
I'm having the same troubles migrating some ARM-Android libraries from 32 to 64 bits.
In the case of GDAL, fortunately I could find pre-built 64 bits binaries:
https://github.com/eltorio/RtkGps/tree/master/gdal-prebuilt
GDAL java bindings can be found in the libs
folder. That is the gdal.jar
file:
https://github.com/eltorio/RtkGps/tree/master/libs
Answered By - LuisTavares
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.