<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
On the other hand, this is increasingly redundant, what with the increased portability in the system and coming to the system :). And increasingly insufficient, since it doesn't test compilability of the C code.<BR>
<BR>
- Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
From: jay.krell@cornell.edu<BR>To: m3devel@elegosoft.com<BR>Subject: FW: building all platforms regularly?<BR>Date: Wed, 14 Jan 2009 04:16:43 +0000<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
[was truncated]<BR><BR><BR><BR>
<HR id=EC_stopSpelling>
<BR>
From: jay<BR>To: m3devel<BR>Subject: building all platforms regularly?<BR>Date: Wed, 14 Jan 2009 02:57:51 +0000<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
Hi.<BR> <BR>On my system I can<BR> cd m3-sys/m3cc <BR> cm3 -DM3CC_TARGET=platform <BR> cd scripts/python <BR> ./do-cm3-all.py realclean skipgcc <BR> ./do-cm3-std.py platform boot skipgcc <BR> ./boot1.py platform <BR> <BR> <BR>and for pretty much "any" platform it pretty much works.<BR>Ok, on a 32bit host with a 64bit target, there is an error in JV.i3 or such because,<BR>like TextLiteralF.i3, there is a declaration of a maximally sized integer.<BR>This is an easy to fix compiler bug, soon.<BR> <BR> <BR>Ratchet it down to just "min" and it works more, since JV.i3 isn't there.<BR> <BR> <BR>The result of this is a .tar.gz containing assembly source for all the Modula-3 code,<BR>some .h and .c files, and a Makefile and alternate make.sh.<BR>One can takes this to the target system, with a C development environment,<BR>and finish the build, giving you a current cm3, which you can then use to build cm3cg,<BR>and so on. (Some source files are also in the archive and updatesource.sh, but that's<BR>not relevant to this email; they are typically edited files when doing a new port.)<BR> <BR> <BR>So, my point is, maybe this should be run kind of like the Tinderboxes?<BR>Spitting out current archives of all "active" platforms, regularly?<BR> <BR> <BR>It is not as "good" as the Tinderbox.<BR>There might still be errors in the C, link errors, test failures.<BR>But it is pretty good.<BR> <BR>It gets a bit more testing across platforms and provides a good up to date start.<BR> <BR> <BR>And then, the list of "active" targets needs to be identified.<BR> <BR> <BR>Oh, I forgot to mention, this only currently works for platforms for which<BR>there is m3-sys/cminstall/src/config-no-install/platform, and NT386.<BR>The others give an error about not liking the "unconfigured" config files<BR>in the neighboring config directory.<BR> <BR> <BR>Also, the .tar.gz is presently put at the root, which isn't right.<BR>It works ok on Windows.<BR> <BR> <BR> - Jay<BR><BR></body>
</html>