RFR: 8303796: Optionally build fully statically linked JDK image

Jorn Vernee jvernee at openjdk.org
Sun Apr 30 19:09:23 UTC 2023


On Sun, 30 Apr 2023 18:34:12 GMT, Alan Bateman <alanb at openjdk.org> wrote:

> A possible direction on this is for the build to create a set of packaged modules with the .a files, then have an alternative image builder in jlink that integrates with the native linker. Combined with other parts in Jiangli's slides/proposal, it would mean that jlink could produce a single executable that would work for both the JDK or any set of modules.

It seems that letting jlink do the linking is also a requirement for user provided modules (.jmods) that contain native libraries (as is the case for instance with jextract). We don't know about those libraries when building the JDK.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/13709#issuecomment-1529114550


More information about the core-libs-dev mailing list