c:\smlnj\but any valid directory name of your choosing will do.
In NT, environment variables are usually set via ControlPanel->System. In Windows 95, they may be set per session with the DOS set command from a shell prompt or, more persistently, by placing a set command in the autoexec.bat startup file:
set SMLNJ_HOME=c:\smlnj\ set PATH=c:\smlnj\bin\
c:\smlnj\> gunzip 110-win32-smlnj.tar.gz
c:\smlnj\> tar -xvf 110-win32-smlnj.tar
ftp.research.bell-labs.com:/dist/smlnj/working/110/110-smlnj-lib.tar.ZTo install it, create a SML/NJ src directory (i.e. c:\smlnj\src) and decompress and untar the above smlnj-lib distribution file there.
c:\smlnj\bin\sml-cm.batSet the Working Directory to the directory in which you want SML/NJ to start.
If you desire to modify the compiler itself, you'll need some additional tools to build it. (The executables in the distribution suffice for compiling SML programs.)
Compiling the runtime system requires the following tools:
It should be straightforward to build with other compilers, assemblers, and "make" utilities (see src\runtime\objs\makefile.win32 and src\runtime\objs\mk.x86-win32).
nmake /f mk.x86-win32in SML/NJ's src\runtime\objs directory. This will create run.x86-win32.exe which is usually placed in the smlnj\bin\.run directory.
ftp.research.bell-labs.com:/dist/smlnj/working/110/110-bin.x86-win32.tar.Z(You can create this set of bin files by retargeting the compiler, with CM, to cross-compile, e.g. from a Unix platform, to the win32 OS.) Place bin.x86-win32 in src\sml-nj. Set the working directory to src\sml-nj and, from a ksh prompt, issue the command:
xmakeml -boot bin.x86-win32This will produce the image sml.x86-win32 which is usually placed in bin\.heap
buildis issued in the respective tool directory. Note that SML/NJ's bin directory must be in the path for the default build command to find the compiler and tools.