
<!DOCTYPE html><html><head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

  </head>

  <body>

    <br>

    <br>

    <div class="moz-cite-prefix">On 20/12/2024 14:20, David Lloyd wrote:<br>

    </div>

    <blockquote type="cite" cite="mid:CANghgrR0YdnjzkC+gzCHMU5tmuaB1XkjmWVFj=k+7UpMfAeiQg@mail.gmail.com">

      

      <div dir="ltr">:<br>

        <div><br clear="all">

        </div>

        <div>

          <div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I see, so it

            seems that there still would have to be a parent-child

            relationship (possibly transitive) between the layer

            containing the service consumer and the layer containing the

            service provider, correct? And the provider must be in a

            parent layer. I.e. using `jlink` doesn't magically make this

            constraint disappear, which is what I thought was being

            implied.</div>

          <br>

        </div>

      </div>

    </blockquote>

    At this time, the jimage format doesn't support more than one

    version of a module and jlink only supports link-time optimizations

    for the boot layer. There is a mountain of interesting work that

    could be done there, including link-time optimizations for

    applications that are launched in child layers.<br>

    <br>

    -Alan<br>

  </body>

</html>