[M3devel] install and C code

[Jay K]

We do have the bootstrap archives, but they onlybuild cm3/mklib. We need to extend them to buildeverything, and either carry all of the Modula-3source, or carry everything as assembly source.

I was thinking about that a while ago for a whileand couldn't decide, like, among cmake or automakeor makefiles for each directory.

 - Jay

From: jay.krell at cornell.edu
To: m3devel at elegosoft.com
Date: Tue, 5 Jan 2016 10:44:22 +0000
Subject: [M3devel] install and C code




I finally had a minor epiphany.

 
Ignoring the C backend, to the extent that
the system contains C code, "install" should
actually recompile all the C code, using
the user's intended compilation environment.
 

This would clear up various incompatibilities
that exist. i.e. with m3core.lib.sa and m3.lib.sa
and the bootstrapping procedure.
 
 
 
The 3.6 distribution did this.
It actually distributed assembly source and C source and then
did assembly/compilation/linking on the user machine.
assembly is close to "binary", but this had advantages.
It also solved the "origin" problem, back in the time before
origin was widely supported -- i.e. link with full paths on Unix systems.
 
 
I don't have the energy now, but we really could use a bit of a rewrite here.
 

 - Jay 
 		 	   		  

_______________________________________________
M3devel mailing list
M3devel at elegosoft.com
https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20160105/d78e7990/attachment-0002.html>