This comments in this file are based on MKS Toolkit for developers,
version 9.6, running on Windows XP Professional, SP3.  The configure
script was generated by GNU Autoconf 2.68.

The most recent build of units with the Toolkit (using Microsoft Visual
C/C++ 6.0, and Visual C/C++ Express 9.0 and 10.0) was for version 2.11
on 24 March 2014.

The system on which the build was done had /bin as a symbolic link to
C:/Program Files/MKS Toolkit/mksnt.

  -- Jeff Conrad (jeff_conrad@msn.com) 1 April 2014

Configure
---------
Configure will fail unless invoked as

    ./configure PATH_SEPARATOR=';'

Compilation
-----------
The MKS version of make ignores suffix rules in Makefile unless the line

    .POSIX:

appears in Makefile before any suffix rules.  This target is also
required for the currency updater units_cur to run properly from
Makefile.  The configure script attempts to detect the Toolkit by
running mksinfo, and if this succeeds, the .POSIX target is added.  If
you have the MKS Toolkit and it somehow is not detected, you should add
this line manually.

Behavior of PAGER
-----------------
The MKS versions of more and less do not recognize '+n' as an option to
display a file beginning at line n, so help <unit> from within units
will fail.  If configure is able to detect the Toolkit by running
mksinfo,

    -DHAVE_MKS_TOOLKIT

is added to the DEFS in Makefile.  If you have the MKS Toolkit and it
somehow is not detected, you should add this manually.

Install Program
---------------
If the PATH at shell invocation uses the backslash as the path
separator, and you have a BSD-compatible install program, the Makefile
may have the incorrect entry

    INSTALL = c:usrlocalbin/install.exe -c

Add the slashes to get

    INSTALL = c:/usr/local/bin/install.exe -c

Giving a PATH with forward slashes in a file given by ENV will have no
effect because configure unsets that variable, and the file will not be
read.

Python and units_cur
--------------------
If python is installed, a copy of python.exe must be placed in /usr/bin
so the shell can find it.  Alternatively, you can change the first line
of units_cur to specify the location of the python executable.

The complete pathname in Makefile may contain backslashes; for example,

  PYTHON = C:\usr\bin/python.exe

The build will fail unless the backslashes are changed to forward
slashes:

  PYTHON = C:/usr/bin/python.exe
