Platform affinity for. So files

Platform affinity for. So files

It was a simple question, but it was not clear to me at the time that the distinction had resulted in a lot of time spent on testing and modification;

When using the Baidu Map SDK there are two library file jar packages and a C + +. So file

In my own demo project This is no problem, directly get the map GPS information I want, and then I put this demo function in the project when there is a problem, and wasted me a long time to solve

In this project, using the. So file has four packages, Armeabi, ARMEABI-V7A, MIPS, x86, of course, you certainly know the difference between these files, but the same configuration in the same demo, but not the normal use of the. so file-- Libocsdk4d.so, and do not report any errors, originally thought is the source program problem, after the test found to be. So file path problem, in the demo because only the Armeabi folder is given, and in this folder gives the. so file, so can be used directly, and in the project because there are four different platform files Clip In this case, you must place the. So file in all four folders, or in the. so file of the platform used by your model, so that you can use the. so file, which is very similar to layout adaptation, but it's very different, but it's a lot more important to know where the problem is.

The correct placement location:

Platform affinity for. So files