<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>make-dist makes everything.<BR> <BR><br>It makes a "min" distribution and an "all" distribution.<br>Hopefully you can read it through it makes semi-reasonable sense.<BR> <BR><br>This is all my doing -- which is to say, I quite like it,<br>but not necessarily anyone else.<BR> <BR><br>min as I recall, is just the compiler: cm3, cm3cg, mklib, config, m3core, libm3 <br> (mklib is only for NT386 target, but it is small and innocuous)<BR> <BR><br>all is everything, including min<BR> <BR><br>I don't like the confusion and purported complexity of breaking<br>things down into several medium sized packages, with dependencies.<BR><br> <BR>I want more of a "one stop shop", granted, a big one, that<br>gives everyone stuff they won't use.<BR> <BR> <BR> <BR>But I compromised and it makes to things.<br><BR> <BR> <BR>It makes roughly speaking .tar.gz files.<BR>Or .zips for some targets.<BR>Or compresed tar, depending on what compressor it can find, and bundles<BR>them into .deb files. But .deb files are little more than .tar.gz or .tar.bz2 or .tar.xz<BR> <BR> <BR>upgrade.sh also builds everything<BR><br> <BR>When I wrote it to upgrade.py I missed that significant aspect, and it only builds the compiler.<br>Perhaps I should rename it to upgrade-min.py and then have upgrade-all.py.<BR> <BR><br>You can mimic upgrade.sh with ugprade.py && do-cm3-all.py realclean skipgcc && do-cm3-all.py buildship<br>(skipgcc is just an optimization to avoid some duplicate work)<BR> <BR><br>I never use any of the .sh files.<br>I found them to hard to understand and not portable enough.<br>i.e. I'd rather install Python on Windows than Cygwin.<br>I suspect Bourne shell is just not worth learning to program in.<BR> <BR><br>I had rewritten them in .cmd for Windows, but wanted one set of scripts.<BR><br> <BR>cvs is pretty awful.<br>I'm still more productive in it than git, but I expect that will change.<br>But ok. cvsup can work. The error is for a trivial thing.<BR><br> - Jay<br><br><br><br> <BR><div>> Date: Mon, 1 Jun 2015 10:25:11 +0200<br>> From: adacore@marino.st<br>> To: jay.krell@cornell.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] m3cgc1: fatal error: *** bad M3CG version stamp (0x100), expected 0x110<br>> <br>> On 6/1/2015 10:15, Jay K wrote:<br>> > This is very good progress.<br>> > Thank you for your speed and patience.<br>> > <br>> > <br>> > And the error is kind of minor and uninteresting. Yes, I understand, it<br>> > is fatal. Everything should just work to completion.<br>> > <br>> > <br>> > See IsDarwin here:<br>> > <br>> > <br>> > https://github.com/modula3/cm3/blob/master/m3-sys/cminstall/src/config-no-install/cm3cfg.common <br>> > <br>> > <br>> > cvsup is fiddling around how to use zlib.<br>> > See here:<br>> > https://github.com/modula3/cm3/blob/master/m3-tools/cvsup/suplib/src/m3makefile<br>> > <br>> > <br>> > and surely cvsup isn't interesting any more? Who is using cvs?<br>> <br>> NetBSD and OpenBSD for starters.<br>> <br>> <br>> <br>> > You can delete m3-tools/cvsup.<br>> > or change the scripts to skip it<br>> > or update cm3cfg.common to be more up to date.<br>> <br>> I'd like to keep it, it's the best source for cvsup.<br>> <br>> I thought make-dist.py was just going to bootstrap (e.g. minimal<br>> required). Is it actually building everything?<br>> <br>> <br>> I was intending to run do-cm3-min.sh buildship, do-cm3-std.sh buildship,<br>> do-cm3-caltech-parser.sh buildship after make-dist.py completed.<br>> <br>> John<br>> <br></div> </div></body>
</html>