-
Bug
-
Resolution: Fixed
-
P3
-
12
-
b13
There's a lot of weird stuff going on with libjli and the launchers. Most of it stems from the old build system, which was just copied verbatim into the new build system. This is the final part of getting JLI to behave like most other libraries.
This patch will:
* store libjli in the standard lib directory, not in a "jli" subdirectory.
* remove dead code for filtering ergo files, which do no longer exist
* use file extension to show type (ObjectiveC), rather than -x objective-c.
* use more common constructs in setting up the native compilation arguments.
* clean out unused flags and arguments.
This patch will:
* store libjli in the standard lib directory, not in a "jli" subdirectory.
* remove dead code for filtering ergo files, which do no longer exist
* use file extension to show type (ObjectiveC), rather than -x objective-c.
* use more common constructs in setting up the native compilation arguments.
* clean out unused flags and arguments.
- relates to
-
JDK-8211288 app-image fails to find JLI lib at launch time
- Resolved
-
JDK-8213362 [macOS] Could not find libjava.dylib error when initializing JVM via JNI_CreateJavaVM
- Closed