
 Tested on MS Windows 2000/XP with SDL library, failed to install GGI.
 Mouse cut/paste is supported, but CCE/SDL on MS Windows still have lots of
 problems(can't run telnet/ftp?)

 1. How to install SDL/GGI and CCE on MS  Windows?

    1) Install cygwin GNU environment
	   http://www.cygwin.com
	   You need to install binutils, gcc, perl, bash packages.

    2) Looks like SDL is easier to install on Windows,
	   you can just download the binary release from http://www.libsdl.org,
	   you need to make sure that CCE can find SDL.dll library.
	   You can also build SDL library from source using MinGW32 or Cygwin(Although
	   I failed to build SDL using Cygwin *_* ).

       But since CCE requires Cygwin's terminal emulation(MinGW doesn't support
	   that), so CCE can only be built with Cygwin.

	   Also, you need to make sure CCE's configure script can get SDL's
	   header and library, I put it in cygwin's /usr/i686-pc-cygwin/include
	   and /usr/i686-pc-cygwin/lib.
	   
    3) If you want to use GGI, you need to install GGI/GII from source:
	    http://www.ggi-project.org
	   install GII first, then GGI, you need to configure it this way:

	   ./configure --without-x --with-directx
	   make install

       You may need to fix a few things if it doesn't compile. I failed to compile
	   it on my Win2000 and WinXP.

	4) Install CCE
	   ./configure     # It will automatically detect SDL and GGI
	   make install
	   
	   
  2. Win32 GNU tools (for Win32 PE format executables)
  
   You can download and install Windows self-hosted GNU toolchain or do
   cross-compiling on your Linux machine.

   http://www.cygwin.com    a Linux-like environment for Windows
        based on cygwin1.dll(a Linux emulation layer)
        Cygwin/XFree86(XWin) also works on all Windows platform
        A pretty complete GNU on Win32 platform.
		
		If your program uses Cygwin API, then your executable cannot run without
		cygwin1.dll. It's not possible to statically link with a Cygwin library 
		to obtain an independent, self-contained executable. You can either link
		MSVCRT*.DLL or cygwin1.dll, they are mutually exclusive. cygwin1.dll 
		is a C library which provides a Unix-style API, so your source code doesn't
		need to change.

        Cygwin supports terminal handling and /dev/ptmx style pseudo terminals.
        For POSIX devices, cygwin supports the following devices: /dev/null,
		/dev/zero, /dev/tty, /dev/ttyX, /dev/ptmx, /dev/comX(serial port)
		/dev/windows(Windows message queue), /dev/random and /dev/urandom.

        For cross-compiling, configure binutils/gcc this way:
		   ./configure --target=i586-pc-cygwin
		(but you do need to install the C lib header for gcc)


   http://www.mingw.org   Minimalist GNU for Windows
        Allow you to produce native Windows programs that do not rely on any 3rd-party 
		DLLs. Just download and install these packages on Windows:
		    MinGW(including GNU binutils/gcc toolchain, headers and libraries)
			MSYS(including bash and other Unix utilities)

        MinGW doesn't provide too much POSIX emulation for Win32, there is no termios.h
		(No terminal-related stuff), no /dev/* emulation like Cygwin. MinGW includes lots
		of Win32 header files and libraries, so your program can link directly with
		Win32 DLLs. It seems MinGW is faster than Cygwin(bash/gcc,etc)?

		For cross-compiling, configure binutils/gcc this way: 
		  ./configure --target=i586-pc-mingw32


   http://pw32.sourceforge.net   Posix-over-win32 layer
        based on DJGPP's runtime library, similar to cygwin and mingw32
        binutils 2.14 doesn't support i586-pc-pw32


