[fpc-devel] sqlite support for Android

Felipe Monteiro de Carvalho felipemonteiro.carvalho at gmail.com
Mon Apr 2 12:34:16 CEST 2012


In Android a dlopen operation without a full path will fail:

  sqliteDLL:=DlOpen('libsqlite.so',RTLD_LAZY); ==> fails
  sqliteDLL:=DlOpen('libsqlite3.so',RTLD_LAZY); ==> fails
 ==> fails
 ==> works
  sqliteDLL:=DlOpen('/system/lib/libsqlite.so',RTLD_LAZY); ==> works

So the existing sqlite bindings fail. The simples solution would be
hardcode for Android /system/lib/libsqlite.so but this is somewhat of
a grey area since this library is not guaranteed to exist. The other
option is placing it in our lib folder, but then you need to pass the
entire path for dlopen and this path will necessarely change with each
project, for example: '/data/data/com.pascal.lcltest/lib/libsqlite.so'
constains the name of the project "com.pascal.lcltest"

The solution would be to make this library name a variable then, but
this won't work because the sqlite bindings need to support static
linking too =O So maybe a variable only in the case of dynamic

Well, so basically I am just sending this e-mail to start talks about
what kind of solution would be accepted, maybe someone has better
ideas then I had. I am tempted towards:

{$ifdef Android}
  libsqlite3 = '/system/lib/libsqlite.so';

Which is what I already commited to fpc4android

Felipe Monteiro de Carvalho

More information about the fpc-devel mailing list