WIN32(native compilers, not gnu-win32) notes added by jwo@netcom.com 96.11.17 //John is no longer able to actively participate in mud++ project. //He has done most of work, but developement of mud and few ommited #ifdefs //caused that this still need some tinkering. //I tried to correct this things to allow painless run on WIN32 system. //For now it works only under Symantec C++ 7.2 - I haven't check anything else. //Artur <abies@pg.gda.pl> 1. - configure doesn't run on windows/dos systems. Edit config.h directly to suit your compiler. // there is an example in src/win32/config.h - copy it to src/ directory 2. - Create a new console project, then add all the *.cc (and *.h if necessary) files and build the project. If you have problems with mpdaemon.cc then do not include it in the project as it is not necessary (daemon functions are handled differently in WIN32 native v0.16 port). // also do not include vector.cc If you must use a makefile you will need to create your own, otherwise your programming environment (MSVC, Borland, Symantec, Watcom etc...) should spit one out specific to their compiler. There are some extra files needed for mud++ as there are functions not a part of the standard libraries of the native compilers that I use. They are in mud++/src/win32. Add them to the project. in src/win32: source files: crypt.c crypt_util.c (these are part of ufc-crypt) header files: crypt.h ufc-crypt.h (again part of ufc-crypt) (the crypt files should be placed in the ./src directory; they provide password encryption. It may be possible to code around the need for them but this would leave your player files vulnerable :) // no need for placing crypt.h in src/ header files: telnet.h (put it in the ..../include/arpa directory) (you can get telnet.h from a GNU compiler distribution for UN*X) // again, leave them in win32/ It is important to make sure that your compiler DEFINES the following at compile time: WIN32, WIN32_LEAN_AND_MEAN, WIN32_EXTRA_LEAN, _MT. Type these in if it doesn't. WIN32_EXTRA_LEAN is used in MSVC++ but I am not sure about SC++, but it doesn't hurt to define it anyway. // In SC++ you also have to include winsock.lib - add it to project manually