Hello Bob.

17 Oct 03 23:05, you wrote to me:

 MG>> Yes. I tried to compile it with Open Watcom, and got
 MG>> tons of errors. As Bo Simonsen posted, all the stuff
 MG>> that's Linux specific needs to be changed with an
 MG>> "#ifndef Unix" statement in order for it to compile
 MG>> correctly. I'm no programmer, so I haven't a clue as to
 MG>> what needs to be changed.

 BJ> The maximus / squish code was developed and compiled with an older Watcom
 BJ> compiler (pre-Open Watcom), and used DMAKE for a make subsystem.  Without
 BJ> understading the environment (defines, etc.) that needs to be setup, you
 BJ> probably will fail to get a good compile.  You also need to pick up
 BJ> either Bison or Yacc to compile maximus, and for Win32 and OS/2
 BJ> environments, may also need to pick up an old copy of MASM (which used to
 BJ> be available on one of Microsoft's web sites).  With out proper defines,
 BJ> the code will fail to compile.  With Watcom and the proper defines, you
 BJ> could cross compile the code for DOS, OS/2 and Win32 systems on a single
 BJ> system, for both 16-bit and 32-bit target binaries.  No, I haven't done
 BJ> this with the GPL'ed Maximus code, because I never got DMAKE to properly
 BJ> run under OS/2....  I'd now want to use GNU Make instead of DMAKE, which
 BJ> will still require re-work of some of the make files for using in a DOS,
 BJ> OS/2 and/or Win32 environment.

Too much work, and way too far beyond my simple grasp of how compiling
works. If I have someone tell me, "this code will compile properly
with this compiler", then I can do it. Any more complicated than that,
and I'm lost.


--- GoldED/W32 3.0.1