On Sun 2010-01-31 00:18, Mvan Le (3:800/432) wrote to All:

 ML> I have successfully compiled all Maximus 3.02 overlayed DOS and
 ML> Win32 source executables as per "MaximusSourceDoc.doc" on Windows
 ML> XP using Watcom C/C++ Version 11c and the "h\nt" headers and
 ML> "lib386\nt" libraries from Version 10.6.  

MaximusSourceDoc.doc on the CVS tree should really be corrected.  Although
it should be converted to text first.  CVS and binary (.doc) formats don't
really work well when you're trying to use 'diff'...

Why are the NT headers and libaries from 10.6 required?  Is it because
11.0C doesn't supply them?  I didn't notice you were using 11.0C when I
read your message the first time so you can obviously disregard the link to
11.0C in my previous message because you obviously have it.  Maybe it'll
help other people though.

What happens if you use the NT headers/libs from OpenWatcom 1.0 instead? 
Assuming they exist.  An academic question if we can use OW 1.0 to build
the entire thing.

It's long overdue, but it'd be great if we could get to a point where you
could just do a CVS checkout and start the build 
process without needing to extract max-3.03-etc.tar.gz beforehand. 
Actually the DOS/OS2/Win builds probably don't need that, just the Linux
version.  Strange that it's a requirement though, because there's no source
code in there.  In fact it seems to build fine if you just do a cvs
checkout, then "mkdir maximus/install_tree".

Anyway, it's probably a good idea if you were a member of the Maximus
project on SourceForge, then you could do CVS commits yourself.  Of course
you should avoid doing any major CVS commits until the source has
stabilsied, ie. it builds successfully for all targets.

You can see the list of members here:

https://sourceforge.net/project/memberlist.php?group_id=63593

I think you'd just need to contact one of the admins and ask politely to be
added.  :-)

--- timEd/Linux 1.11.b5