Mined compilation

Go into the "src" subdirectory.
Select a makefile closest to your operating system. (For your 
convenience, you may set a link ln -s makefile.<selected> makefile).

The following makefiles work on Unix:
	makefile.linux	on Linux
	makefile.bsd	on BSD-like systems
	makefile.sun	on SunOS and other System V Unix systems
	makefile.hp	on HP-UX (quite similar to .sun)
	makefile.osx	on Mac OS X (similar to .bsd)
	makefile.curses	on Unix, but should not be used (less functionality)
The following makefiles are meant for DOS-based compilation:
	makefile.cygwin	for the cygwin Unix-compliant environment
	makefile.dj	for djgcc
		compiles on plain DOS, same executable runs in Windows 
		DOS box, supporting long file names under Windows 98/2000
	makefile.djc	for djgcc with PDcurses (not needed)
	makefile.emx.curses	for EMX with curses
	makefile.emx		for EMX without curses, does not work
	makefile.emx.window	was an attempt for window mode, doesn't work
These are only include files:
	mkinclud.mak
	mkinclud.gcc
	mkinclud.cc
Turbo-C 3.0 uses mined.prj. Turbo-C 2 uses minedtc2.prj - source files 
have to be converted to MSDOS line ends first.
For VMS, compile the source files mentioned in vms-link.com by hand, 
then use that script for linking.


If you don't find a working makefile, try to adapt one, especially 
select a suitable screen handling mode as commented in the makefile.
5 basic modes are available:
* termio (Unix)
* sgtty (Unix, BSD-style)
* curses (Unix and others, but not recommended)
* conio (DOS-based, detected automatically)
* ANSI (selected if none else chosen and conio not detected)
Also consider the other settings, e.g. the sysV variable (see makefile).


As many people seem to prefer it, a special note about curses:
Older Unix curses implementions can be considered quite a piece of junk.
They used to behave quite clumsy at output, much more than direct 
terminal control, and they dared to obstruct the use of 8-bit character 
sets long in the post-ASCII ages.
The curses option was originally only built in for a quick port to VMS 
where it is automatically selected.
The newer ncurses library does not have these problems any more but still 
has two major drawbacks: It is less flexible with respect to colour 
configuration (selecting a foreground colour only (with default 
background) or background colour only are not established with 
reasonable documentation at the interface) and there is no UTF-8 
capable implementation released yet in order to support Unicode.


A special note on DOS versions:
The cygwin environment provides an emulation of a Unix 8-Bit character set 
so diacritic characters entered in this version are different from those 
entered in the EMX or djgcc or Turbo-C versions.
Mouse support is now available for all DOS-based versions - in principle; 
for cygwin, there still seems to be an encoding problem.
With djgcc, a dual-mode version can be compiled that supports long file 
names if run in a Windows DOS box - at least under Windows 98 and 2000.
The promise of the EMX environment to be able to compile dual-mode 
applications does not hold - at least not with curses.

A DOS binary version precompiled with djgcc is available from the 
mined web site http://towo.net/mined/.
Users of cygwin or EMX can easily compile a version themselves.
If you want to recompile the djgcc version, you can make a stand-alone 
version with "make alone"; it uses the smaller memory management module 
"pmode" which is available from the djgcc distribution. See the makefile 
for the URL.
