The initialization process for the Java platform uses the architecture name to locate the correct binary for the platform. We, apparently, do not support the name "amd64"
Edited on 18/Oct/2022: I see no evidence that Java, in release 2.7 or later, has used the architecture name to select a LiteCore library. Reopend to solicit further input from @Michael Fene
Activity
Show:
Blake Meike October 26, 2022 at 4:44 PM
Closing. I cannot reproduce the problem described here.
Blake Meike October 21, 2022 at 5:25 PM
@Michael Fene: do you have any input, here?
Blake Meike October 18, 2022 at 5:07 PM
Edited
@Michael Fene: do you have evidence that this issue persists? It looks to me as if this was fixed in v3.0
It appears that the ticket is mis-labelled. The issue that drove the rewrite of the library loading code, which originated in the forum post above, was a user misunderstanding and nothing to do with supported ABIs.
On examining the code I do not see evidence that any version of CBL-Java will fail loading a library because it is running on an AMD platform.
Java copies the native libraries from resources in the jar file to the file system files named <scratch dir>/<lib hash>/<lib name>, where:
<scratch dir> is the directory named in the 3rd argument to CouchbaseLite.init. It defaults to being a directory named "CouchbaseLiteTemp" in the directory in which CBL is running
<lib hash> is the MD5 signature for both binary libraries. This is necessary to assure proper versioning
<lib name> is the name of the library, LiteCore and LiteCoreJNI, as mangled appropriately for the OS, using the Java function System.mapLibraryName.
Michael Fene July 25, 2022 at 6:07 AM
This issue re: AMD64 support for java sdk states: resolved. Although it appears the issue continue to persist. Can you point me to the resolution details?
Blake Meike April 2, 2021 at 8:06 PM
This should be fixed in couchbase/couchbase-lite-java-common @ac8b4e48c
Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.
The initialization process for the Java platform uses the architecture name to locate the correct binary for the platform. We, apparently, do not support the name "amd64"
Edited on 18/Oct/2022:
I see no evidence that Java, in release 2.7 or later, has used the architecture name to select a LiteCore library. Reopend to solicit further input from @Michael Fene