[M3devel] release testing on Windows XP

[Randy Coleburn]

Ok, so here is what I've done:
1.  deleted PKGS
2.  scripts/win/upgrade.cmd
3.  scripts/win/do-cm3-std.cmd
 
These work, except that I had to modify pkginfo.txt as follows:
1.  Removed all m3-www packages (web & proxy)
2.  Removed all cvsup packages
 
If I left these in there, I got failures.
 
BTW, I've rebuilt cm3ide and it is running on Windows XP with no crashes so far.
 
Now, if (?) the pkginfo.txt file is what is driving the process, it appears that each line in the file has a package and one or more tags, e.g. min std core.  I assume the order of packages in pkginfo.txt is the correct build order.  If these statements are true (and I'm asking you to verify), I will try to write a simpler CMD script that deals with the building process using pkginfo.txt as the "input control file".
 
Regards,
Randy Coleburn

>>> Jay K <jay.krell at cornell.edu> 7/19/2009 5:52 PM >>>
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

CONFIDENTIALITY NOTICE:  This email and any attachments are intended solely for the use of the named recipient(s). This e-mail may contain confidential and/or proprietary information of Scientific Research Corporation.  If you are not a named recipient, you are prohibited from making any use of the information in the email and attachments.  If you believe you have received this email in error, please notify the sender immediately and permanently delete the email, any attachments, and all copies thereof from any drives or storage media and destroy any printouts of the email or attachments.

EXPORT COMPLIANCE NOTICE:  This email and any attachments may contain technical data subject to U.S export restrictions under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR).  Export or transfer of this technical data and/or related information to any foreign person(s) or entity(ies), either within the U.S. or outside of the U.S., may require export authorization by the appropriate U.S. Government agency prior to export or transfer.  In addition, technical data may not be exported or transferred to certain countries or specified designated nationals identified by U.S. embargo controls without prior export authorization.  By accepting this email and any attachments, all recipients confirm that they understand and will comply with all applicable ITAR, EAR and embargo compliance requirements.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090719/6346c67b/attachment-0002.html>