[M3devel] status report on Windows XP

[Jay K]

Bear in mind some features:

 do-pkg (via sysinfo) does a good job of finding compiler/linker

   You can copy that, but I also intend to move it into the config files if I can.

   Though not sure e.g. path/lib/include-search is easy there.

   And I don't want the config files every time to launch a bunch of processes to do the probing.

   Maybe move the logic to cm3 itself. Maybe.

 

 sets the version defines when building cm3, by reading the version file

   The python, .sh, and preexisting .cmd do that. You can copy the code out though.

 

Is a little more easily extended -- no builtin list of package groups, but not a big deal.

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.

Ditto for do-cm3-std.py wrapping do-pkg.py.

 

The structuring is not all that natural I agree, I copied the structuring of the .sh files fairly faithfully,

and then improved things by introducing pkginfo.txt.

 

Some of the generalizations aren't useful.

I'm going to remove the purported support for PM3 and M3 from pylib.py for example.

 

My Python code is still missing a nifty feature that Olaf added to the .sh where you can

pass extra parameters on to cm3.

 

Yeah we do need to filter out more packages.

The package list has grown since I last used the .cmd files and pylib.py has its own list,

so I might not be building those packages on any platform.

I'll see about filtering in the m3makefiles. That is shared across all the .sh/.py/.cmd.

 

.cmd code is generally a maintenance nightmare. The more you write, the bigger the problem.

Again you might want to try writing JScript. It is much more natural. It can be slow

but you aren't likely to notice here. And it is very portable to Windows.

You can wrap it up within a .cmd file if you want, or have a one liner .cmd that calls cscript foo.js.

 

 - 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/bae32913/attachment-0002.html>