Fixing installation process
[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
996c9412
AC
16Modify the parameters in settings and settings.sml as appropriate for
17your system.
dc3b1a7f 18
c0a3b488
AC
19If it is possible for you to modify a file /etc/mlt.conf, then you
20can edit this file to set various options related to locations of
21important files on your file system. In particular, you may want to
22set the 'compiler', 'lib', and 'sml' options (documented in the
23manual) if you have SML/NJ installed somewhere besides /usr/local/sml
24or the mlt src directory somewhere besides /usr/local/share/mlt/src.
25If you can't modify /etc/mlt.conf, then you can change the first
26variable definition in src/config.sml to a different path, or you can
27leave it as is and provide all configuration in the local mlt.conf
28file for each project.
29
c0a3b488
AC
30These changes may be made for you by a fancy configuration program in
31a future release.
32
33
34========
35Building
36========
37
38All sources may be built by running the build script in this
39directory. It does a clean re-build of all source files and stabilizes
40all libraries produced. The build script is not appropriate for use
41during development. Use the standard SML/NJ CM mechanisms if you are
42changing 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
45out yet.]