Each of the following four ‘make’ targets creates an executable named scm. Each target takes its build options from a file with an ‘.opt’ suffix. If that options file doesn't exist, making that target will create the file with the ‘-F’ features: cautious, bignums, arrays, inexact, engineering-notation, and dynamic-linking. Once that ‘.opt’ file exists, you can edit it to your taste and it will be preserved.
If the build fails, then ‘build scm4’ instead. If the dumped
executable fails to run, then send me a bug report (and use
‘build scm4’ until the problem with dump is corrected).
If the build fails, then ‘build scm5’ instead. If the dumped executable fails to run, then send me a bug report (and use ‘build scm5’ until the problem with dump is corrected).
If the above builds fail because of ‘-F dynamic-linking’, then (because they can't be dynamically linked) you will likely want to add some other features to the build's ‘.opt’ file. See the ‘-F’ build option in Build Options.
If dynamic-linking is working, then you will likely want to compile most of the modules as DLLs. The build options for compiling DLLs are in dlls.opt.
Xlibmodule; SCM Language X Interface.
wbmodule; B-tree database implementation. Compiling this requires that wb source be in a peer directory to scm.