[M3devel] release testing on Windows XP

[Jay K]

The "all" versions of all the scripts fail to compile (all as in Python, .sh, .cmd).

Try "std".

 

All the scripts are also a bit identically loose in how they find "projects".

  They look for something/src/m3makefile where something contains what they are after.

  It is a bit fragile.

Except for your .cmd files which are more precise.

 

There is also a bug in all the scripts that adding new packages to the source tree fails.

The PKGS files needs a version number in its name and if PKGS-correctionversion doesn't

exist the scripts should delete PKGS* and regenerate.

We only recently got a centralized version file though and I didn't want to implement

this until that was in.

 

 - Jay

 


Date: Sun, 19 Jul 2009 17:43:02 -0400
From: rcolebur at scires.com
To: jay.krell at cornell.edu; m3devel at elegosoft.com
Subject: Re: [M3devel] release testing on Windows XP




do-cm3-all.py:  This crazy python animal is now trying to compile my examples folder!
It fails, of course, and doesn't go any farther.
Regards,
Randy Coleburn

>>> Jay K <jay.krell at cornell.edu> 7/19/2009 5:31 PM >>>
Try deleting the PKGS file of course. Management of that file is poor, across all the scripts.
Almost any version of Python will do and I highly recommend it. .cmd is a terrible programming language and Python is an excellent one. Python is also very portable. I use all the same automation across a variety of platforms.
(I still haven't gotten it to work on OpenBSD/sgimips and I do sometimes test Olaf's .sh code.)
JScript isn't so bad, and it is "built in" on essentially all Windows installs (as long as there is IE), but it isn't portable at all for command line use to Python wins again. I understand the desire to not install anything at all, but this one install provides tremendous value. Sometimes a dependency is worth it.
 
 - Jay
 




Date: Sun, 19 Jul 2009 16:55:53 -0400
From: rcoleburn at scires.com
To: m3devel at elegosoft.com; rcoleburn at scires.com
Subject: Re: [M3devel] release testing on Windows XP


For #3 below, I went to scripts/win and ran upgrade.cmd.  No problems there.  
 
Then I tried do-cm3-std.cm3, but it fails complaining that the m3-www\web package is missing.
 
I suspect these scripts may not be up to date.  
 
Alas, I'm going to try to download python 2.6 for Windows since that is what Jay seems to be using these days.  Then I'll try running his python scripts and see how it fares.  
 
But, I again think we need to not depend on python scripts for cm3 on Windows.  I am willing to work on the .CMD scripts.
 
--Randy Coleburn

>>> "Randy Coleburn" <rcoleburn at scires.com> 7/19/2009 2:58 PM >>>

Olaf / Jay / et al:
 
I am back from my trip and thought I would try to test out what we have for Windows XP platform.
 
My plan is:
 
1.  Backup my current cm3 tree and sandbox.
2.  Update my local sandbox copy of all CM3 from the CVS repository.
3.  Use my current cm3 to rebuild everthing in the updated sandbox.  In so doing, I will ship back to my cm3 installation thereby updating it to be current.
4.  Use my updated cm3 to build and test a number of my programs.
5.  Report results to m3devel
 
Regards,
Randy Coleburn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090719/f3c422df/attachment-0002.html>