Change BUILDING to only discuss 110.49+
[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
16If it is possible for you to modify a file /etc/mlt.conf, then you
17can edit this file to set various options related to locations of
18important files on your file system. In particular, you may want to
19set the 'compiler', 'lib', and 'sml' options (documented in the
20manual) if you have SML/NJ installed somewhere besides /usr/local/sml
21or the mlt src directory somewhere besides /usr/local/share/mlt/src.
22If you can't modify /etc/mlt.conf, then you can change the first
23variable definition in src/config.sml to a different path, or you can
24leave it as is and provide all configuration in the local mlt.conf
25file for each project.
26
27You should also edit the paths in the simple install script in this
28directory if you want to install system-wide binaries and scripts to
29somewhere besides /usr/local/bin.
30
31These changes may be made for you by a fancy configuration program in
32a future release.
33
34
35========
36Building
37========
38
39All sources may be built by running the build script in this
40directory. It does a clean re-build of all source files and stabilizes
41all libraries produced. The build script is not appropriate for use
42during development. Use the standard SML/NJ CM mechanisms if you are
43changing the code and don't want to recompile everything each time.
44
45[There is probably a better way to do this, but I haven't figured one
46out yet.]