[M3devel] mklib in upgrade.py ...

[Jay K]

mklib: I fixed it to compile long ago, broke it recently, fixed it recently.
There is a dependency on m3core having the Win32 typedefs/defines.
Which it has had for years.


If we really need to stay compatible with very old versions, I can copy
those typedefs/defines into mklib, again.


mklib's utility on non-Windows systems is hypothetical at this point.
If we had/used a cross linker and cross C compiler, then mklib would
help round out a cross build solution. Without a cross linker, it is kind of pointless.
(Then again, with a cross linker and C compiler, we'd probably have "cross ar",
though mklib does a bit more than that..)


I guess I can filter mklib out of for non-Windows.
But more likely I will leave it in.
I'd rather copy the few relevant types/constants into mklib.
Or just require everyone to have an up to date m3core..
There are so many things in the system that do work, but people keep
trying to use old libraries/toolsets.
The odbc duplication is another example -- a bunch of identical files
except for calling convention, calling convention previously being
an error on non-Windows systems, but for years now being ignored instead.



 - Jay



> To: jay.krell at cornell.edu
> Date: Mon, 14 Oct 2013 11:58:31 -0700
> From: mika at async.caltech.edu
> CC: m3devel at elegosoft.com
> Subject: [M3devel] mklib in upgrade.py ...
> 
> 
> And now I see that mklib talks a lot about WinNT.  I suspect I have no
> use for it???  I took it out of upgrade.py since it doesn't compile and
> breaks the upgrade procedure... perhaps there should be a test somewhere
> to ensure it won't get compiled on non-Windows systems?  Or fix it so it
> does compile.. 
> 
>      Mika
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20131014/28218351/attachment-0002.html>