--- dpark <[EMAIL PROTECTED]> wrote:
> My first question was why all the native jar files are different (they
> at least have different file sizes) when, supposedly, they're all
> interchangeable and do the same thing. I've verified at least that
> the linux native jar file runs just fine on my mac.
They may have been built by different Java SDKs.
> But that new libsqlitejdbc.so now fails to load (obviously) on my 32
> bit linux machines (the pre-packaged binary was fine though). I tried
> putting both .so files in the same directory (renaming one of them to
> -32bit.so or something), but I discovered that the .so file will not
> load unless it has exactly the expected name--no renaming allowed,
> which meant the two could not coexist.
>
> So since the linux driver seems unable to load in both platforms, the
> sensible thing to me would be to just have the driver look for
> different names for each, so that we can have a directory that
> contains all four drivers (two .so's, the .jnilib, and the .dll).
> Maybe something just like -i386.so and -x86_64.so or something.
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.
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
