Fwiw, doing that kind of linkage trickery is likely to result in an app that
breaks in the future, especially since the SQLite library is not a public
part of the NDK.

On Thu, Sep 3, 2009 at 9:19 PM, Chris Stratton <[email protected]> wrote:

>
> On Sep 3, 11:44 pm, JavaNut <[email protected]> wrote:
> > Thanks for the information on that.  Yes, I looked some more and it
> > looks like SQLite is in C.  I have to figure out how to approach this
> > situation.
>
> /system/lib/libsqlite.so looks to be some 300k in size... making a
> custom version would be unpleasant but not beyond the realm of
> possibility.
>
> You could look into the documentation or source and see if there's any
> way that file access is hookable, without having superuser permission
> to create an encrypted file system driver...
>
> I was doing some reading earlier this evening on runtime linkers, and
> the usual linux one can be told to preload a library such that the
> functions contained in it would over-ride those contained in demand
> loaded libraries; not clear if this can override what is effectively a
> private internal function... or if that capability is available in
> android's rather unique linker...
>
> Pretty soon we'll be talking about a custom runtime linker that loads
> up a patched version of the existing sqlite...  there must be a better
> way?
>
> >
>


-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to