<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16850" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px">
<DIV>Jay:</DIV>
<DIV> </DIV>
<DIV>I'm not quite sure what all the various "do-pkg.cmd" and "do-cm3-*.cmd" scripts actually do. Some of the code is pretty complex and I decided it would take me longer to figure it out than to just write a new script.</DIV>
<DIV> </DIV>
<DIV>Anyway, you didn't answer my questions, so I've experimented to come up with something that seems to work for the current cases in PkgInfo.txt.</DIV>
<DIV> </DIV>
<DIV>I've uploaded a new file "do-cm3.cmd" that processes the "PkgInfo.txt" file based on my understanding of that file's format. I've tested it locally and it seems to work for me.</DIV>
<DIV> </DIV>
<DIV>This one .CMD file is meant to be an alternative to all of the various "do-pkg.cmd" and "do-cm3-*.cmd" files.</DIV>
<DIV> </DIV>
<DIV>Here are examples of how it could be called:</DIV>
<DIV>cd "scripts\win"</DIV>
<DIV>do-cm3 std buildship</DIV>
<DIV>do-cm3 game clean buildship</DIV>
<DIV>do-cm3 game realclean build ship</DIV>
<DIV>do-cm3 comm depends</DIV>
<DIV>do-cm3 all buildship</DIV>
<DIV> </DIV>
<DIV>There is a block of code labeled "SetupCM3" in "do-cm3.CMD" that expects to call my "cm3SetupCmdEnv.cmd" file, but if you don't use this file, simply comment-out this block of code or set CM3_DoneSetup=TRUE at the beginning of the block to prevent it from running.</DIV>
<DIV> </DIV>
<DIV>If anyone tries my new script, let me know if you experience any problems and I'll try to fix them.</DIV>
<DIV> </DIV>
<DIV>Finally, if I want to adapt my "do-cm3.cmd" script to also handle the work of "upgrade.cmd", I'm going to need someone to explain to me the compilation and shipping order for the upgrade process.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy Coleburn<BR><BR>>>> <jay.krell@cornell.edu> 7/20/2009 9:56 PM >>><BR>do-pkg.cmd already does this doesn't it?<BR>It is looking for substring matches against paths or somesuch like <BR>the .sh code.<BR>Not actually package names.<BR><BR> - Jay (phone)<BR><BR>On Jul 20, 2009, at 5:42 PM, "Randy Coleburn" <rcoleburn@scires.com> <BR>wrote:<BR><BR>> I am nearing completion of a "do-cm3.cmd" script for Windows 2000/XP <BR>> that operates based on the "scripts/PkgInfo.txt" file.<BR>><BR>> I have a question about the format of the "scripts/PkgInfo.txt" file.<BR>><BR>> Most of the lines in this file identify a package by name as the <BR>> first entry on the line. A few of them also provide a relative path <BR>> to this package.<BR>><BR>> If the source tree is rooted at "sandbox\cm3", we have subfolders <BR>> "m3-sys", "m3-games", etc.<BR>><BR>> How do we know in which unique subfolder each package is located?<BR>><BR>> For example, "m3cc" is in "sandbox\cm3\m3-sys\m3cc"<BR>> while, "netobj" is in "sandbox\cm3\m3-comm\netobj"<BR>><BR>> Then we have in PkgInfo.txt lines like:<BR>> "paneman/kemacs" which is in "sandbox\cm3\caltech-parser\paneman <BR>> \kemacs"<BR>> "m3-games/badbricks" which is in "sandbox\cm3\m3-games\badbricks"<BR>><BR>> I can see the need for the relative path for "paneman/kemacs", but <BR>> "m3-games/badbricks" seems to break with the established pattern. <BR>> Is this an error in the current PkgInfo.txt file?<BR>><BR>> Regards,<BR>> Randy Coleburn<BR><BR></DIV></BODY></HTML>