[M3devel] cross "compiling"

[Jay]

This may be obvious to everyone and so inadequate as to be useless, but I just had a minor idea and proved it correct.
 
Even if you don't have a backend, C compiler, linker, etc, you can still compile the Modula-3 code for any target from any target.
 
If you just put return 0 in the config file for backend, compile_c, link, make_lib, assembly, you can at least run the front/middle ends.
 
For example I just compiled m3core and libm3 for Solaris. That would have caught my DatePosix.m3 error, though that sort of change was maybe one that just can't be commited without an available machine. (I'm still not sure how to do these things. You can only change what you have, or send diffs around and wait for the all clear, or you can make a best effort and hope..)
 
Obviously it only affords a certain minimal amount of checking.
But it is perhaps something.
 
IN FACT...maybe it is enough testing that the tinderboxes should do it, for all platforms deemed "supported"?
I don't think you can ship, but you can buildlocal. (I built libm3, depends on m3core).
 
I'll push this a bit further.
 
IF this is deemed useful, maybe a compiler switch?
 
 - Jay
_________________________________________________________________
Need to know the score, the latest news, or you need your Hotmail®-get your "fix".
http://www.msnmobilefix.com/Default.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080226/975f8ae8/attachment-0001.html>