<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>On 2024-01-18 10:44, Julian Waters wrote:</p>
<blockquote type="cite" cite="mid:VmQK7VhlKKAcwfO-VsLlZbFmi99wbp5alBjuxLL58vs=.9b5895de-d52d-4416-b672-eb034c23972e@github.com"><span style="white-space: pre-wrap">If I understand you correctly, this new hypothetical system would replace autoconf as such?</span>
<pre class="moz-quote-pre" wrap="">
configure -> autoconf -> compiled configure -> make
to
configure -> compile Java -> Java configure program -> make
</pre>
</blockquote>
<p>Yep, something like that. With a thin shell wrapper (think
gradlew) to launch `java Configure` or something like that. If the
progress with multi-file java launching continues properly, we
might even be able to skip the compile step.</p>
<p>I have a prototype sketch I've been working on from time to time.
This discussion actually inspired me to go back to it and see if I
can convert into a more proper proof-of-concept. </p>
<p>/Magnus<br>
</p>
</body>
</html>