Support #6340
move JNI and native dependencies into the jar
0%
Related issues
History
#1 Updated by Greg Shah almost 2 years ago
This article describes a technique to load our own native libraries (and other native dependencies) from our own jar file:
The idea is to bundle multiple versions of the native binaries into the jar, extract them to a temp dir at runtime and then load them from there. This is a clever way to make it easier to deploy. There can also be a fall-back to use the current approach if there is any failure in the extraction or loading.
In addition to our own libp2j.so
/p2j.dll
we might want to also bundle libffi
so that we can eliminate that dependency from the install requirements.
In combination with #4550, #5167 and #5568, we could eliminate all of the local install requirements. A critical requirement for the runtime system will be that a writable temp directory is available (with a certain amount of space available). That is OK.
#2 Updated by Greg Shah almost 2 years ago
- Related to Support #4549: reduce/eliminate installation dependencies added