<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
"usable source" as in editable and then rebuildable?<br>Ok, that I see.<br><br>> No, only partial sources (historically the IFs, in CM3 modules, too --<br><br>I didn't realize the history but I did notice the option and considered<br>it to shrink the distributions, but the source is useful for debugging.<br><br>> but no makefiles for example).<br><br>To serve as examples and to make it buildable? Ok.<br><br>Then I like it. :)<br><br>Like, it is gentler than having newbies use cvs, and<br>gets the versions that match their binaries.<br><br>Change the release notes?<br>Well, er, um, I guess the "ws" form on Windows might be nice too.<br><br>You can say this:<br>install.cmd:<br>SetLocal<br>set root=%~dp0<br>set pkgs=<br>set pkgs=%pkgs% m3-sys/cm3<br>set pkgs=%pkgs% m3-sys/m3quake<br>
set pkgs=%pkgs% m3-libs/m3core<br>etc.<br><br>for %%a in (%pkgs%) do call :F1 %%a || exit /b 1<br>goto :eof<br><br>:F1<br>set b=%1<br>
rem replace forward slashes with backward slashes<br>
set b=%b:/=\%<br>
cd %root%\%b% || exit /b 1<br>
cm3 -ship || exit /b 1<br>
goto :eof<br><br>There is an implied label :eof at the end of files.<br>"goto :eof" is how you "return".<br><br>You can also create<br>pkgs.txt:<br>m3-sys/cm3<br>m3-sys/m3quake<br>etc.<br><br>install.cmd<br>SetLocal<br>set root=%~dp0<br>
for /f %%a in (%root%\pkgs.txt) do call :F1 %%a || exit /b 1<br>goto :eof<br><br>
:F1<br>set b=%1<br>rem replace forward slashes with backward slashes<br>set b=%b:/=\%<br>
cd %root%\%b% || exit /b 1<br>cm3 -ship || exit /b 1<br>
goto :eof<br>
<br><br>I guess ideally pkgs.txt is identical files across all platforms, though<br>maybe alter the newlines, and then you write install.sh and install.cmd<br>that are constant and look for pkgs.txt "next to" them?<br><br><br>This "advanced" sort of cmd won't work on Win9x but it should work<br>pretty far back on NT like to 4.0 or maybe 3.51.<br><br><br>For Win9x compat, and actual even for sanity, you'd might want to consider<br>install.js or install.vbs. .js is a pretty ok language and .cmd is awful after<br>a few lines.<br><br>I guess I'll do this -- install.cmd + pkgs.txt.<br><br> - Jay<br><br>> Date: Sat, 18 Jul 2009 13:56:25 +0200<br>> From: wagner@elegosoft.com<br>> To: jay.krell@cornell.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: RE: [M3devel] Release notes comments<br>> <br>> Quoting Jay K <jay.krell@cornell.edu>:<br>> <br>> >> > 4. I don't understand the "-bin-ws-" concept of "precompiled user<br>> >> > workspace" and how it would be useful. Please elaborate.<br>> >><br>> >> Copied from a mail I sent to Jay some weeks ago:<br>> ><br>> > I actually still don't understand that.<br>> Strange.<br>> <br>> > Archiving up the installed form includes source.<br>> No, only partial sources (historically the IFs, in CM3 modules, too --<br>> but no makefiles for example).<br>> <br>> > What is the value of doing the ship/directory reorganization upon install?<br>> Easiest way to combine complete _usable_ source and binary products.<br>> <br>> > However, it is kind of a step toward a distribution that includes assembly<br>> > for everything and then assemble, c compile, link, and ship on the target.<br>> > (You might even use autoconf/libtool, though their powers will be severely<br>> > constrained by the presence of assembly.)<br>> > And such a distribution is easily cross built for all targets in one <br>> > fell automated<br>> > swoop on one host, good, valuable that way.<br>> ><br>> >> Yes, I haven't spent much thought on Windows until now. I hoped that<br>> >> you or Jay will do that. Of course I've also overseen the install.cmd<br>> >> scripts for Windows :-/ Should we use cmd or bat? Could somebody<br>> >> quickly provide the equivalent of this loop, so that I can<br>> >> automate it?<br>> <br>> > There are recent builds on <br>> > http://modula3.elegosoft.com/cm3/uploaded-archives/index.html.<br>> ><br>> > http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-NT386-d5.8.1.zip<br>> > http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-NT386-d5.8.1.msi<br>> > http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-NT386-d5.8.1.msi<br>> > http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-NT386-d5.8.1.zip<br>> ><br>> > as well as:<br>> > http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-AMD64_LINUX-d5.8.1.deb<br>> [...]<br>> ><br>> > sorry..<br>> <br>> That's not what we're talking about. We're talking about installation<br>> archives for Windows for RC2 as they are described in the release<br>> notes. There are none.<br>> <br>> I can build them myself, but then it will take another couple of weeks.<br>> No hurry needed though, as we haven't fixed RC2 yet.<br>> <br>> Olaf<br>> -- <br>> Olaf Wagner -- elego Software Solutions GmbH<br>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<br>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<br>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<br>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<br>> <br></body>
</html>