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