More un-hardcoding
[bpt/mlt.git] / BUILDING
... / ...
CommitLineData
1===================
2System requirements
3===================
4
5Compiling the mlt tool requires a "working version" of SML/NJ. It's
6best to use version 110.49 or later. Earlier versions have
7incompatibilities, bugs, or both. You may have problems with any
8version whatsoever, though, since this stuff uses some SML/NJ compiler
9internals, and they may change often.
10
11
12=============
13Configuration
14=============
15
16Modify the parameters in settings and src/settings.sml as appropriate
17for your system.
18
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
30You should also edit the paths in the simple install script in this
31directory if you want to install system-wide binaries and scripts to
32somewhere besides /usr/local/bin.
33
34These changes may be made for you by a fancy configuration program in
35a future release.
36
37
38========
39Building
40========
41
42All sources may be built by running the build script in this
43directory. It does a clean re-build of all source files and stabilizes
44all libraries produced. The build script is not appropriate for use
45during development. Use the standard SML/NJ CM mechanisms if you are
46changing the code and don't want to recompile everything each time.
47
48[There is probably a better way to do this, but I haven't figured one
49out yet.]