[M3devel] status report on Windows XP

[Jay K]

[truncated..no big deal...]





 


From: jay.krell at cornell.edu
To: rcoleburn at scires.com; m3devel at elegosoft.com
Subject: RE: [M3devel] status report on Windows XP
Date: Tue, 21 Jul 2009 11:49:21 +0000



These should all be ok now except for m3cc.
Hopefully you can filter it out somehow.
After the 5.8 release I'll split up the NT386 platforms into three platforms and then the m3cc/src/m3makefile can do the filtering naturally (allowing it for I386_CYGWIN and I386_MINGW/MINGNUWIN but disallowing it for I386_NT).
 
 
tcl has other problems imho, I disabled it for Win32.
It is a massive clone of C headers from years ago and could easily be out of date.
The right fix anyway is probably to add Tcl to SYSLIBS -- venturing on actually needing the config files to actually vary per user..
 
 
pp requires lex/yacc or flex/bison, and would give an error indicating so.
Now it just does nothing if they are missing.
 
 
caltech requires termios/cfmakeraw, I put in a do-nothing version of Win32 and fixed the Posix version to be safer, more portable, and more and less efficient. I don't know why it was disabling the garbage collector so I removed that.
Was that termios.i3 actually portable? Are the structs of known size across all Posix systems and the constants constant?
A better Win32 implementation probably isn't difficult.
 
 
It'd be great if anyone could sign up and say they use this caltech parser stuff, including the terminal stuff it is doing (try removing the cfmakeraw call, notice a difference, and test the Win32 version and verify it doesn't work great..?)
Actually I ran some of the executables there and got some usage statements and an array index out of bounds or such in some gui code..
 
 
 - Jay

 


Date: Tue, 21 Jul 2009 03:38:53 -0400
From: rcoleburn at scires.com
To: m3devel at elegosoft.com
Subject: Re: [M3devel] status report on Windows XP


I should restate that these are the packages where "cm3 -build" terminated with an errorlevel set.
 
There are some other packages that do not build because their m3makefile is configured not to build for NT386 platforms, or for some other reason, e.g. X-Windows not available.
 
Regards,
Randy

>>> "Randy Coleburn" <rcoleburn at scires.com> 7/21/2009 3:26 AM >>>

This report is for Windows XP Professional, Service Pack 3, using Microsoft Visual Studio 2008 Version 9.0.21022.8 RTM, and Microsoft .NET Framework Version 3.5 SP1.
 
I've updated my local sandbox to be current with the CM3 CVS repository at elego.  I've performed a "upgrade.cmd" to upgrade my cm3 compiler to the latest version.
 
I kept running into problems with "scripts\win\do-cm3-std.CMD" stopping short with an error message.
 
So, I built my own "do-cm3.CMD" and used it to rebuild everything.
 
Here are the packages that fail to build (I think most of these are not supported currently on Windows):
m3-sys\m3cc
m3-libs\tcl
caltech-parser\term
caltech-parser\paneman
caltech-parser\paneman\kemacs
caltech-parser\drawcontext\dcpane
caltech-parser\drawcontext\kgv
caltech-parser\parserlib\klexlib
caltech-parser\parserlib\klex
caltech-parser\parserlib\kyacc
caltech-parser\parserlib\kext
caltech-parser\parserlib\parserlib\test
m3-tools\pp

I've also built tested CM3IDE and it seems to work fine on Windows.  I've even tried it with the "examples" folder missing and it still works fine.
 
I'll try to check out how well some of the other packages run as time permits.
 
Regards,
Randy Coleburn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090721/d185efe1/attachment-0002.html>