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