<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>We do have the bootstrap archives, but they only</div><div>build cm3/mklib. We need to extend them to build</div><div>everything, and either carry all of the Modula-3</div><div>source, or carry everything as assembly source.</div><div><br></div><div><br></div><div>I was thinking about that a while ago for a while</div><div>and couldn't decide, like, among cmake or automake</div><div>or makefiles for each directory.</div><div><br></div><div><br></div><div> - Jay</div><br><br><div><hr id="stopSpelling">From: jay.krell@cornell.edu<br>To: m3devel@elegosoft.com<br>Date: Tue, 5 Jan 2016 10:44:22 +0000<br>Subject: [M3devel] install and C code<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">I finally had a minor epiphany.<br><br> <br>Ignoring the C backend, to the extent that<br>the system contains C code, "install" should<br>actually recompile all the C code, using<br>the user's intended compilation environment.<br> <br><br>This would clear up various incompatibilities<br>that exist. i.e. with m3core.lib.sa and m3.lib.sa<br>and the bootstrapping procedure.<br> <br> <br> <br>The 3.6 distribution did this.<br>It actually distributed assembly source and C source and then<br>did assembly/compilation/linking on the user machine.<br>assembly is close to "binary", but this had advantages.<br>It also solved the "origin" problem, back in the time before<br>origin was widely supported -- i.e. link with full paths on Unix systems.<br> <br> <br>I don't have the energy now, but we really could use a bit of a rewrite here.<br> <br><br> - Jay <br> </div>
<br>_______________________________________________
M3devel mailing list
M3devel@elegosoft.com
https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel</div> </div></body>
</html>