RFR: 8311302: Allow for jlinking a custom runtime without packaged modules being present [v18]

[Severin Gehwolf]

On Mon, 11 Mar 2024 13:24:54 GMT, Erik Joelsson <erikj at openjdk.org> wrote:

> Based on that I agree with the choice of using a configure argument.

Thanks. The intention is that without the extra configure argument you'd get `jdk-image` as is today. Not modified. *With* `--enable-runtime-link-image` the result of what ends up in `images/jdk/lib/modules` is changed in a way that it allows linking without needing the packaged modules. Everything else should remain the same. That includes generated CDS archives, `src.zip` and so on. That is why it currently ends up in the same output directory. I hope that is acceptable as requiring downstream distributors to assemble the artefacts by hand (using the linkable jimage from some other location) would be more error prone.

My mental model for this would be similar to JVM features (e.g. `--with-jvm-features`). That also keeps the original location of `libjvm` but adds/removes features.

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

PR Comment: https://git.openjdk.org/jdk/pull/14787#issuecomment-1988501066