[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-2d-dev
Subject:    Re: RFR: 8303796: Optionally build fully statically linked JDK image
From:       Jorn Vernee <jvernee () openjdk ! org>
Date:       2023-04-30 19:09:23
Message-ID: -LR0qy8lzfy0N6sksIJNnVxAIesh0yQmRNYrG5pvG2I=.52637aed-bbc2-4ea8-a134-d148c91f2953 () github ! com
[Download RAW message or body]

On Sun, 30 Apr 2023 18:34:12 GMT, Alan Bateman <alanb@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


[prev in list] [next in list] [prev in thread] [next in thread]