1 This port requires IBM C/C++ and the IBM TCPIP library. It 2has probably only been tested with the CVS client. Local CVS might or 3might not work, and the server would definitely not work. You'll need 4to edit the makefile to reflect your system's paths (unless you're our 5customer for this port, in which case the paths are correct because we 6did the port on your machine. :-) ). You also may need to comment out 7the "Makefile" rule in emx/Makefile to avoid a complaint about 8../config.status not existing. You also might need to edit srcdir to 9be "." and top_srcdir to be "..". 10 11 That should be all -- edit the makefile, do "make" and get 12os2\cvs.exe. Assuming you have edited the `install_dir' variable in 13the Makefile, you may type "make install-cvs" to put cvs.exe in the 14right place. 15 16 If the makefile has linefeeds only at the end of lines, make 17(at least the port of GNU make that I have) will interpret it 18differently. This is (IMHO) a bizarre behavior, but you need to 19convert the linefeeds to CRLF pairs (editing the file with an editor 20such as emacs will generally do this). 21 22 There are two compiler warnings in os2/popen.c which we haven't 23figured out the cause of. Other than that there probably aren't a whole 24lot of warnings (but there might be a few). 25Report bugs to <bug-cvs@gnu.org>. 26 27 28 29Some notes on the watcom port: 30------------------------------ 31 32You need the OS/2 TCPIP developers toolkit to translate the sources. 33This is not as bad as it sounds, since the toolkit is on your OS/2 34CD. 35 36To compile the sources, enter 37 38 wmake -f watcom.mak 39 40at the OS/2 prompt. 41 42The executable created by the watcom compiler does *not* need a runtime 43DLL. 44 45 46 Uz (uz@musoftware.com) 47 48Credits: 49 50Original port in 1995 by Karl Fogel <kfogel@cyclic.com>. 51