BUILDING

   1 ===================
   2 System requirements
   3 ===================
   4
   5 Compiling the mlt tool requires a "working version" of SML/NJ. It's
   6 best to use version 110.49 or later. Earlier versions have
   7 incompatibilities, bugs, or both. You may have problems with any
   8 version whatsoever, though, since this stuff uses some SML/NJ compiler
   9 internals, and they may change often.
  10
  11
  12 =============
  13 Configuration
  14 =============
  15
  16 Modify the parameters in settings and settings.sml as appropriate for
  17 your system.
  18
  19 If it is possible for you to modify a file /etc/mlt.conf, then you
  20 can edit this file to set various options related to locations of
  21 important files on your file system. In particular, you may want to
  22 set the 'compiler', 'lib', and 'sml' options (documented in the
  23 manual) if you have SML/NJ installed somewhere besides /usr/local/sml
  24 or the mlt src directory somewhere besides /usr/local/share/mlt/src.
  25 If you can't modify /etc/mlt.conf, then you can change the first
  26 variable definition in src/config.sml to a different path, or you can
  27 leave it as is and provide all configuration in the local mlt.conf
  28 file for each project.
  29
  30 These changes may be made for you by a fancy configuration program in
  31 a future release.
  32
  33
  34 ========
  35 Building
  36 ========
  37
  38 All sources may be built by running the build script in this
  39 directory. It does a clean re-build of all source files and stabilizes
  40 all libraries produced. The build script is not appropriate for use
  41 during development. Use the standard SML/NJ CM mechanisms if you are
  42 changing the code and don't want to recompile everything each time.
  43
  44 [There is probably a better way to do this, but I haven't figured one
  45 out yet.]