
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">That could be done, but it would require more work with no obvious benefit.<div><br></div><div>Only the Java launcher needs to be universal from the perspective of the OS.</div><div><br><div><br></div><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Mar 7, 2024, at 1:24 PM, Michael Hall <mik3hall@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Not directly in response to your prior. But curious, are you doing something like described here?<div><br></div><div><a href="https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary">https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary</a><br id="lineBreakAtBeginningOfMessage"><div><br></div></div>If not why not?<div><br></div><div>It indicates</div><div><br></div><div><blockquote type="cite"><span style="caret-color: rgb(29, 29, 31); color: rgb(29, 29, 31); font-family: "SF Pro Text", system-ui, -apple-system, BlinkMacSystemFont, "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 17px; letter-spacing: -0.374px; background-color: rgb(255, 255, 255);">For universal binaries, the system prefers to execute the slice that is native to the current platform. </span></blockquote><br></div><div>Isn’t that saying the OS will just do the right thing? </div></div></div></blockquote></div><br></div></div></body></html>