| | 1 | =================== |
| | 2 | System requirements |
| | 3 | =================== |
| | 4 | |
| | 5 | Compiling the mlt tool requires a "working version" of SML/NJ on a |
| | 6 | POSIX system. It's best to use version 110.49 or later. Earlier |
| | 7 | versions have incompatibilities, bugs, or both. You may have problems |
| | 8 | with any version whatsoever, though, since this stuff uses some SML/NJ |
| | 9 | compiler internals, and they may change often. |
| | 10 | |
| | 11 | |
| | 12 | ============= |
| | 13 | Configuration |
| | 14 | ============= |
| | 15 | |
| | 16 | Modify the parameters in settings as appropriate for your system. |
| | 17 | |
| | 18 | These settings may be determined for you automatically by a fancy |
| | 19 | configuration program in a future release. |
| | 20 | |
| | 21 | |
| | 22 | ======== |
| | 23 | Building |
| | 24 | ======== |
| | 25 | |
| | 26 | All sources may be built by running the 'build' script in this |
| | 27 | directory. It does a clean re-build of all source files and stabilizes |
| | 28 | all libraries produced. The build script is not appropriate for use |
| | 29 | during development. Use the standard SML/NJ CM mechanisms if you are |
| | 30 | changing the code and don't want to recompile everything each time. |
| | 31 | |
| | 32 | The 'install' script installs the 'mlt' program to the BINDIR |
| | 33 | specified in settings. You can also copy the generated mlt.conf file to |
| | 34 | /etc or wherever else you specified for the DEFAULT setting. |
| | 35 | |
| | 36 | [There is probably a better way to do this, but I haven't figured one |
| | 37 | out yet.] |
HCoop / bpt / mlt.git / blame_incremental