<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
> Yeah we do need to filter out more packages. <BR><BR>
If you look for "FilterOnePackage" in pkginfo.cmd you can see this support.<BR>
I'll see about moving it to the m3makefiles instead though.<BR>
I'm not sure it deals with the slashes in some of the package paths either.<BR>
Well..err..clearly not, but not hard to fix. Anyway, I'll see about the m3makefiles.<BR>
<BR>
- Jay<BR> <BR>
<HR id=stopSpelling>
From: jay.krell@cornell.edu<BR>To: rcoleburn@scires.com; m3devel@elegosoft.com<BR>Date: Tue, 21 Jul 2009 08:05:54 +0000<BR>Subject: Re: [M3devel] status report on Windows XP<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
Bear in mind some features:<BR> do-pkg (via sysinfo) does a good job of finding compiler/linker<BR> You can copy that, but I also intend to move it into the config files if I can.<BR> Though not sure e.g. path/lib/include-search is easy there.<BR> And I don't want the config files every time to launch a bunch of processes to do the probing.<BR> Maybe move the logic to cm3 itself. Maybe.<BR> <BR> sets the version defines when building cm3, by reading the version file<BR> The python, .sh, and preexisting .cmd do that. You can copy the code out though.<BR> <BR>Is a little more easily extended -- no builtin list of package groups, but not a big deal.<BR>Look at how do-cm3-std.sh and do-cm3-std.cmd are both just a few lines that wrap do-pkg.sh and do-pkg.cmd.<BR>Ditto for do-cm3-std.py wrapping do-pkg.py.<BR> <BR>The structuring is not all that natural I agree, I copied the structuring of the .sh files fairly faithfully,<BR>and then improved things by introducing pkginfo.txt.<BR> <BR>Some of the generalizations aren't useful.<BR>I'm going to remove the purported support for PM3 and M3 from pylib.py for example.<BR> <BR>My Python code is still missing a nifty feature that Olaf added to the .sh where you can<BR>pass extra parameters on to cm3.<BR> <BR>Yeah we do need to filter out more packages.<BR>The package list has grown since I last used the .cmd files and pylib.py has its own list,<BR>so I might not be building those packages on any platform.<BR>I'll see about filtering in the m3makefiles. That is shared across all the .sh/.py/.cmd.<BR> <BR>.cmd code is generally a maintenance nightmare. The more you write, the bigger the problem.<BR>Again you might want to try writing JScript. It is much more natural. It can be slow<BR>but you aren't likely to notice here. And it is very portable to Windows.<BR>You can wrap it up within a .cmd file if you want, or have a one liner .cmd that calls cscript foo.js.<BR> <BR> - Jay<BR><BR> <BR>
<HR id=EC_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>