> Have a distinct subdirectory for each platform (linux32/, linux64/ etc)
> and just set your LD_LIBRARY_PATH appropriately for the platform.
>
> Or just change the code below to load whatever shared lib you like:
>
> NativeDB.java:
>
> if (libname == null) libname = System.mapLibraryName("sqlitejdbc");
>
> Either interrogate java.lang.System for the platform or override
> "sqlitejdbc" with a user-provided property of some sort.
What I ended up doing was modifying that try/catch block right below
that line that loads the driver, sticking a second try/catch block
inside of it, so that it starts off trying to load "sqlitejdbc", and
falls back to "sqlitejdbc32" if that fails (probably not the best
name, but whatever). Our setup does kind of necessitate autodetecting
in the driver itself... sometimes we run 32-bit jvm's on 64-bit linux
machines, so detecting the platform and setting paths appropriately
doesn't always lead to the right answer. And as I said before, if the
two linux binaries are really incompatible (ie, there's no way to
compile one that works on both platforms), then maybe something like
this should be the general solution for this project?
I'm set for now though.
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
