<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
These should all be ok now except for m3cc.<BR>
Hopefully you can filter it out somehow.<BR>
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).<BR>
<BR>
<BR>
tcl has other problems imho, I disabled it for Win32.<BR>
It is a massive clone of C headers from years ago and could easily be out of date.<BR>
The right fix anyway is probably to add Tcl to SYSLIBS -- venturing on actually needing the config files to actually vary per user..<BR>
<BR>
<BR>
pp requires lex/yacc or flex/bison, and would give an error indicating so.<BR>
Now it just does nothing if they are missing.<BR>
<BR>
<BR>
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.<BR>
Was that termios.i3 actually portable? Are the structs of known size across all Posix systems and the constants constant?<BR>
A better Win32 implementation probably isn't difficult.<BR>
<BR>
<BR>
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..?)<BR>
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..<BR>
<BR>
<BR>
- Jay<BR><BR> <BR>
<HR id=stopSpelling>
Date: Tue, 21 Jul 2009 03:38:53 -0400<BR>From: rcoleburn@scires.com<BR>To: m3devel@elegosoft.com<BR>Subject: Re: [M3devel] status report on Windows XP<BR><BR>
<DIV>I should restate that these are the packages where "cm3 -build" terminated with an errorlevel set.</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy<BR><BR>>>> "Randy Coleburn" <rcoleburn@scires.com> 7/21/2009 3:26 AM >>><BR></DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>I kept running into problems with "scripts\win\do-cm3-std.CMD" stopping short with an error message.</DIV>
<DIV> </DIV>
<DIV>So, I built my own "do-cm3.CMD" and used it to rebuild everything.</DIV>
<DIV> </DIV>
<DIV>Here are the packages that fail to build (I think most of these are not supported currently on Windows):</DIV>
<DIV>m3-sys\m3cc<BR>m3-libs\tcl<BR>caltech-parser\term<BR>caltech-parser\paneman<BR>caltech-parser\paneman\kemacs<BR>caltech-parser\drawcontext\dcpane<BR>caltech-parser\drawcontext\kgv<BR>caltech-parser\parserlib\klexlib<BR>caltech-parser\parserlib\klex<BR>caltech-parser\parserlib\kyacc<BR>caltech-parser\parserlib\kext<BR>caltech-parser\parserlib\parserlib\test<BR>m3-tools\pp<BR></DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>I'll try to check out how well some of the other packages run as time permits.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy Coleburn</DIV></body>
</html>