<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'> > > It is true it did not compile with the released non-Windows m3core. <br> > > I fixed that. <BR> > <br> > Not sure I understand, but it sounds like you want to put the github repo <br> > in a state where it can not be built by the 5-8 release? <br><BR> <BR> No. It compiles with 5.8.6 now. I fixed that. <BR> <BR><a href="https://github.com/modula3/cm3/commit/78f21828ad80422b467e31f18c779cebc0a580eb">https://github.com/modula3/cm3/commit/78f21828ad80422b467e31f18c779cebc0a580eb</a><BR>fix for bootstrapping from previous release -- copy in everything used from m3core/winnt.i3<BR> <BR> - Jay<br><br> <BR><div>> Date: Fri, 12 Jun 2015 08:39:33 -0500<br>> From: rodney_bates@lcwb.coop<br>> To: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] mklib disabled<br>> <br>> <br>> <br>> On 06/12/2015 12:21 AM, Jay K wrote:<br>> > > https://github.com/modula3/cm3/blob/master/m3-sys/mklib/src/m3makefile<br>> > > https://github.com/modula3/cm3/commit/3389c3e2b8b320cce060c6620dcd77c4667671f1<br>> > > 1. m3-sys/mklib will not compile without things from m3-libs/m3core/src/win32,<br>> > > 2. m3-libs/m3core/src/win32 will not compile on non-windows targets, using the<br>> > > release compiler.<br>> > > 3. mklib is only used on windows targets anyway.<br>> > > So, omit mklib altogether, except for windows targets.<br>> ><br>> ><br>> > It is true it did not compile with the released non-Windows m3core.<br>> > I fixed that.<br>> ><br>> ><br>> > It is true it is only used when targeting Windows.<br>> ><br>> ><br>> > However I want this the way it was.<br>> > In particular, because w/ it disabled, I have some propensity<br>> > to break Windows-specific aspects of scripts/python, that leaving<br>> > it enabled reveals. It is pretty cheap.<br>> ><br>> ><br>> > Ok?<br>> <br>> Not sure I understand, but it sounds like you want to put the github repo<br>> in a state where it can not be built by the 5-8 release? If so, that is<br>> not OK. The github master branch should always be buildable by the most recent<br>> release. Otherwise, we are just insultingly unwelcoming to anybody who<br>> is not an insider.<br>> <br>> You are an insider. Just change it back the way you want in your working directory<br>> after you do a pull.<br>> <br>> <br>> > - Jay<br>> ><br>> ><br>> ><br>> <br>> -- <br>> Rodney Bates<br>> rodney.m.bates@acm.org<br></div> </div></body>
</html>