% mv cm.tar.gz /usr/local/lisp % cd /usr/local/lisp % tar -zxf cm.tar.gz
Realtime MIDI output from Common Music requires that the Opcode MIDI System first be installed.
MOVE CM.ZIP \LISP CD \LISP PKUNZIP -D CM.ZIP
Patches for various Common Music releases are available for download from
cm-directory "HD:Lisp:CM:" cm-image-name "HD:Lisp:CM:Common Music" syntaxes '(:MIDI :CSOUND) extensions nil save? t
cm-directory "/usr/local/lisp/cm/" cm-image-name "/usr/lisp/bin/cm.dxl" clm-directory "/usr/local/lisp/clm/" cmn-directory "/usr/local/lisp/cmn/" syntaxes '(:MIDI :CLM :CMN) extensions nil save? t
#!/bin/sh # cm script start acl 5.0 with the saved cm memory image exec /usr/local/lisp/acl5.0/lisp -I /usr/lisp/bin/cm.dxlthen make the script executible by doing:
chmod a+x cmThen simply type "cm" to start Common Music. The system will automatically look for "cminit.lisp" customization file in the "-I" directory you specified in the script.
[Note: The double backslash is necessary for DOS style pathnames in Lisp. However, CLISP 1997-09-19 also allows Unix style pathnames to be used in NT and WIN95]
cm-directory "c:\\cm\\" cm-image-name "c:\\cm\\cm.mem" syntaxes '(:midi :csound) extensions nil save? t
c:\clisp\lisp.exe -M c:\cm\cm.mem %1 %2 %3 %4 %5 %6 %7 %8 %9
When build/make-cm.lisp is loaded into lisp it prompts for the informtion it needs to compile, load and save Common Music. The settings you specify will be (optionally) saved in a site configuration file. This file can be used in subsequent builds to save the system exactly the way you specified.
Experienced users can call make-cm directly with the build information specified as keyword arguments to the function. Here is an explanation of the build parameters:
KEYWORD DESCRIPTION DEFAULT VALUE cm-directory Common Music source directory <current directory> cm-image-name The application file to build, if any. <cm-directory>/cm site-directory Directory for site customized files. <cm-directory>/site If you specify a directory other than the default, you must move any scripts from cm/site that you intend to use to your personal site directory. bin-directory Where to put the binaries if you don't <cm-directory> keep them with the sources. pcl-directory If you use PCL (public domain CLOS), NIL set this variable to the PCL source directory. You must have compiled PCL before building Common Music. clm-directory If using CLM, set to the CLM source NIL directory, othwise NIL. clm-bin-directory Set to CLM's binary directory, <clm-directory> defaults to clm-directory cmn-directory If using CMN, set to the CMN source NIL directory, othwise NIL. cmn-bin-directory Set to CMN's binary directory, <cmn-directory> defaults to clm-directory save? If T, make-cm compiles sources and :IF-NO-COMPILE saves the cm application in one pass. If :IF-NO-COMPILE, the build script either compiles sources or loads the binaries and saves the application if no sources needed compilation. If NIL, make-cm script compiles/loads sources but will not save an application. The :IF-NO-COMPILE option results in the smallest application size. syntaxes The list of output syntaxes to build '(:MIDI :CSOUND) into Common Music. Select any from: :MIDI :CLM :CMN :CSound :MusicKit :CMix :CMusic :RT :SGIMix The first syntax in the list becomes the default syntax when the system boots up. You must load clm and cmn before calling make-cm if you want cm to build withto build with either the :CLM or :CMN syntax. capella Whether to include Capella or not. T [MCL only] extensions Optional list of additional files to NIL load.