[M3devel] building all platforms regularly?

[Jay]

Hi.
 
On my system I can
 cd m3-sys/m3cc 
 cm3 -DM3CC_TARGET=platform 
 cd scripts/python 
 ./do-cm3-all.py realclean skipgcc 
 ./do-cm3-std.py platform boot skipgcc 
 ./boot1.py platform  
 
 
and for pretty much "any" platform it pretty much works.
Ok, on a 32bit host with a 64bit target, there is an error in JV.i3 or such because,
like TextLiteralF.i3, there is a declaration of a maximally sized integer.
This is an easy to fix compiler bug, soon.
 
 
Ratchet it down to just "min" and it works more, since JV.i3 isn't there.
 
 
The result of this is a .tar.gz containing assembly source for all the Modula-3 code,
some .h and .c files, and a Makefile and alternate make.sh.
One can takes this to the target system, with a C development environment,
and finish the build, giving you a current cm3, which you can then use to build cm3cg,
and so on. (Some source files are also in the archive and updatesource.sh, but that's
not relevant to this email; they are typically edited files when doing a new port.)
 
 
So, my point is, maybe this should be run kind of like the Tinderboxes?
Spitting out current archives of all "active" platforms, regularly?
 
 
It is not as "good" as the Tinderbox.
There might still be errors in the C, link errors, test failures.
But it is pretty good.
 
It gets a bit more testing across platforms and provides a good up to date start.
 
 
And then, the list of "active" targets needs to be identified.
 
 
Oh, I forgot to mention, this only currently works for platforms for which
there is m3-sys/cminstall/src/config-no-install/platform, and NT386.
The others give an error about not liking the "unconfigured" config files
in the neighboring config directory.
 
 
Also, the .tar.gz is presently put at the root, which isn't right.
It works ok on Windows.
 
 
 - Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090114/6e6ec7e2/attachment-0001.html>