<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'>mklib: I fixed it to compile long ago, broke it recently, fixed it recently.<br>There is a dependency on m3core having the Win32 typedefs/defines.<br>Which it has had for years.<br><br><br>If we really need to stay compatible with very old versions, I can copy<br>those typedefs/defines into mklib, again.<br><br><br>mklib's utility on non-Windows systems is hypothetical at this point.<br>If we had/used a cross linker and cross C compiler, then mklib would<br>help round out a cross build solution. Without a cross linker, it is kind of pointless.<br>(Then again, with a cross linker and C compiler, we'd probably have "cross ar",<br>though mklib does a bit more than that..)<br><br><br>I guess I can filter mklib out of for non-Windows.<br>But more likely I will leave it in.<br>I'd rather copy the few relevant types/constants into mklib.<br>Or just require everyone to have an up to date m3core..<br>There are so many things in the system that do work, but people keep<br>trying to use old libraries/toolsets.<br>The odbc duplication is another example -- a bunch of identical files<br>except for calling convention, calling convention previously being<br>an error on non-Windows systems, but for years now being ignored instead.<br><br><br><br> - Jay<br><br><br><br><div>> To: jay.krell@cornell.edu<br>> Date: Mon, 14 Oct 2013 11:58:31 -0700<br>> From: mika@async.caltech.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: [M3devel] mklib in upgrade.py ...<br>> <br>> <br>> And now I see that mklib talks a lot about WinNT. I suspect I have no<br>> use for it??? I took it out of upgrade.py since it doesn't compile and<br>> breaks the upgrade procedure... perhaps there should be a test somewhere<br>> to ensure it won't get compiled on non-Windows systems? Or fix it so it<br>> does compile.. <br>> <br>> Mika<br></div> </div></body>
</html>