我们能否确保我们的应用程序使用我们的版本 SQLITE 而不是 android 提供的版本.. 通过使用 Android NDK？
[英]Can we make sure that our app uses our version of SQLITE instead of the one which is provided by android.. by using Android NDK?
问题描述
our application is having problems working with default sqlite version provided in Android 2.1.
我们的应用程序在使用 Android 2.1 中提供的默认 sqlite 版本时遇到问题。 So we want to use the customized sqlite version for our App.所以我们想为我们的应用程序使用定制的 sqlite 版本。 So my question is.. if we get the latest sqlite version from SQLITE.org and compile with android NDK, will we be able to invoke the our sqlite library when ever there are database operations happening in our application? So my question is.. if we get the latest sqlite version from SQLITE.org and compile with android NDK, will we be able to invoke the our sqlite library when ever there are database operations happening in our application? ex: if there is a call like "db.execSQL()" in Application code, How are we sure that it is gonna call the custom library?例如：如果应用程序代码中有类似“db.execSQL()”的调用，我们如何确定它会调用自定义库？
1 个解决方案
解决方案1
0 2011-06-07 11:00:41
In addition to building your own sqlite shared object, you will need to replace one or more of the standard java sources from Android with your own (unless you actually just replace the platform's sqlite shared object). In addition to building your own sqlite shared object, you will need to replace one or more of the standard java sources from Android with your own (unless you actually just replace the platform's sqlite shared object). The platform framework loads /system/lib/libsqlite.so automatically.平台框架会自动加载 /system/lib/libsqlite.so。
I would suggest not naming your shared object libsqlite.so.我建议不要命名您共享的 object libsqlite.so。 I've seen Android's dlopen() being told to load two shared objects with different paths but the same name, only to have the first one opened twice.我已经看到 Android 的 dlopen() 被告知要加载具有不同路径但名称相同的两个共享对象，只是将第一个对象打开两次。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.