[LispM-Hackers] Re: [Lispm-cvs] CVS update: e3

[john morrison]

Hi Guys;

Well, that was unexpectedly easy.  I kind of had the idea that it would
be an all-weekend job.

jm@kappa.unlambda.com wrote:
> 
> Date:   Thursday December 20, 2001 @ 19:20
> Author: jm
> 
> Update of /home/cvsroot/e3
> In directory kappa:/tmp/cvs-serv11363
> 
> Modified Files:
>         app.cc types.h
> Log Message:
> Builds and runs under cygwin on Win2K

It seems to produce the exact same results (based upon a VERY cursory
inspection) as the Linux version.

A couple of observations:

(1) I made a sort of nasty change to types.h.  I tried to use
"stdint.h," but on cygwin, it apparently only exists for this entirely
separate "mingw" compilation set which does NOT depend upon cygwin, but
instead depends upon MS DLLs.  (If there are any cygwin jocks on the
list, please help me out here.)  Now, the weird thing was I got REALLY
close (one undefined reference to an iostream routine at link time), but
then (God Bless Google) found out I was doing things completely wrong. 
So, I made the temporary change -- we ("Who's 'we,' paleface?") ought to
change this to use something better.  Believe it or not,
/usr/include/tiff.h on both Linux and Cygwin seems to define some
u8/u16/u32 data types we might use.

(2) I don't know if anybody out there is planning on hacking on e3
(instead of playing solitaire) on his Win98 laptop whilst he's stuck on
an airplane, but Cygwin was pretty easy to install.  It includes cvs
(make and bash), too, which really helped out with this.  However, the
first version I installed didn't have an up-to-date CVS (Google told me
this was a known "whoops," so I knew enough to go get a newer
download).  I would be more than happy to help anyone who is interested
(although why one would want to do this under Windows rather than a Real
Operating System I will never know).  It is also helpful to get the
latest emacs.

(3) I would be interested in what the binary packaging requirements are
for the e3.exe executable are with respect to the rest of the cygwin
dlls.

(4) If nobody else steps up to the plate, I am perfectly willing to be
the Cygwin guy.

(5) The whole fiasco (is a half-hour problem a "fiasco?") with the
"mingw" thing led me to believe that I am going to have some issues
getting win32 stuff called from e3.exe.  I am assuming that I have to do
so in order to open up a window.  When this issue comes to a head in the
future, if nobody else steps up to the plate, I will revisit the build
process.

-jm

-- 
==== John Morrison
==== MAK Technologies Inc.
==== 185 Alewife Brook Parkway, Cambridge, MA 02138
==== http://www.mak.com/
==== vox:617-876-8085 x115
==== fax:617-876-9208
==== jm@mak.com