This document describes the defsystem system definition macro, a portable "Make" facility for Common Lisp.
Support is provided for organizing systems into hierarchical layers of modules, with matching directory structure. Moreover, the components of the system may be listed in any order the user desires, because the defsystem command reorganizes them according to the file-dependency constraints specified by the user. Since it accomplishes this by performing a topological sort of the constraint-graph, cyclical dependencies are not supported (the graph must be a DAG).
Only two operations, compile and load, are currently defined. The interface for defining new operations, however, is simple and extensible.
Though home-grown, the syntax was inspired by fond memories of the defsystem facility on Symbolics 3600 series lisp machines. The exhaustive lists of filename extensions for various lisps and the idea to have one "operate-on-system" function instead of separate "compile-system" and "load-system" functions were taken from Xerox Corporation's PCL (Portable Common Loops) system.
The code for the defsystem facility and this documentation may be found in
The above is almost certainly no longer true. Suggest the following--rpg
The code and documentation for versions three and four (this document applies to version 3) of the defsystem facility may be found in the Sourceforge CLOCC repository.
Written by Mark Kantrowitz, School of Computer Science, Carnegie Mellon University, January 1990.
Please send bug reports, comments and suggestions to email@example.com.
Dunno if the above should be updated. -- rpg
To use this system,
The external interface to the defsystem facility are the defsystem macro and the operate-on-system function. Defsystem is used to define a new system and operate-on-system to compile it and load it. The definition of require has been modified to mesh well with systems defined using defsystem, and is fully backward-compatible.
In addition, the function afs-binary-directory has been provided for immitating the behavior of the @sys feature of the Andrew File System on systems not running AFS. The @sys feature allows soft links to point to different directories depending on which platform is accessing the files. A common setup would be to have the bin directory soft linked to .bin/@sys and to have subdirectories of .bin corresponding to each platform (.bin/vax_mach, .bin/unix, .bin/pmax_mach, etc.). The afs-binary-directory function returns the appropriate binary directory for use as the :binary-pathname argument in the defsystem macro. For example, if we evaluate (afs-binary-directory "foodir/") on a vax running the Mach operating system, "foodir/.bin/vax_mach/" would be returned.
A system is a set of components with associated properties. These properties include the type, name, source and binary pathnames, package, component-dependencies, initializations, and a set of components.
Components may be of three types: :system, :module, or :file. Components of type :system have absolute pathnames and are used to define a multi-system system. The toplevel system defined by the defsystem macro is implicitly of type :system. Components of type :module have pathnames that are relative to their containing system or module, and may contain a set of files and modules. This enables one to define subsystems, subsubsystems, submodules, and so on.
The '91 tech report indicates that there are five types of component. The
three named above plus
believe I'm using the latest code, and it still seems to have all five types
Foreign systems (systems defined using some other system definition tool), may be included by
providing separate compile and load forms for them (using the
keywords). These forms will be run if and only if they are included in a module with no
components. [In some future version of the defsystem facility there will be new component
types corresponding to each possible operation.] This is useful if it isn't possible to
convert these systems to the defsystem format all at once.
As far as I can tell, what is said about foreign systems here is also true of other lisp
systems defined in different defsystem forms. I.e., if the system isn't defined within the
same :components list as you are, then you can't refer to it except as a foreign system. I
give an example of this below.
The name of a component may be a symbol or a string. For ease of access the definition of a system (its component) is stored under the system properties of the symbol corresponding to its uppercase name. If the system name is a symbol, for all other purposes the name is converted to a lowercase string (system names that are strings are left alone). It is usually best to use the string version of a system's name when defining or referring to it. A system defined as 'foo will have an internal name of "foo" and will be stored in the file "foo.system". A system defined as "Foo" will have an internal name of "Foo" and will be stored in the file "Foo.system".
The absolute (for components of type :system) and relative (for all other components) pathnames of the binary and source files may be specified using the :source-pathname and :binary-pathname keywords in the component definition. The pathnames associated with a module correspond to subdirectories of the containing module or system. If no binary pathname is specified, the binaries are distributed among the sources. If no source pathname is given for a component, it defaults to the name of the component. Since the names are converted to lowercase, pathnames must be provided for each component if the operating system is case sensitive (unless the pathnames are all lowercase). Similarly, if a module does not correspond to a subdirectory, a null-string pathname ("") must be provided.
File types (e.g., "lisp" and "fasl") for source and binary files may be specified using the :source-extension and :binary-extension keywords. If these are not specified or given as nil, the makes a reasonable choice of defaults based on the machine type and underlying operating system. These file types are inherited by the components of the system.
At system definition time, every relative directory is replaced with the corresponding cumulative relative pathname with all the components incorporated.
One may also specify the package to be used and any initializations and finalizations. Initializations (specified with the keyword :initially-do) are evaluated before the system is loaded or compiled, and finalizations (specified with the keyword :finally-do) are evaluated after the system is finished loading or compiling. The argument to the keyword is a form which is evaluated. Multiple forms may be evaluated by wrapping a progn around the forms.
The components of a system, module or file are specified with the :components keyword, and are defined in a manner analogous to the way in which a system is defined.
The dependencies of a system, module or file are specified with the :depends-on keyword, followed by a list of the names of the components the system, module or file depends on. The components referred to must exist at the same level of the hierarchy as the referring component. This enforces the modularity of the defined system. If module A depends on a file contained within module B, then module A depends on module B and should be specified as such. Any other use would make a mockery of the concept of modularity. This requirement is not enforced in the software, but any use contrary to it will produce unpredictable results.
Thus the only requirement in how the files are organized is that at the level of each module or system, the dependency graph of the components must be a DAG (directed ACYCLIC graph). If there are any dependency cycles (i.e., module A uses definitions from module B, and module B uses definitions from module A), the defsystem macro will not be able to compute a total ordering of the files (a linear order in which they should be compiled and loaded). Usually the defsystem will detect such cycles and halt with an error.
If no dependencies are provided for the system, modules and files, it may load them in any order. Currently, however, it loads them in serial order. In a future version of defsystem this will probably become a supported feature. [In other words, this feature hasn't been tested to make sure that they files are not accidentally loaded in the opposite order in some cases. It all depends on whether the definition of topological-sort used is a stable sort or not.]
The basic algorithm used is to topologically sort the DAG at each level of abstraction (system level, module level, submodule level, etc.) to insure that the system's files are compiled and loaded in the right order. This occurs at system definition time, rather than at system use time, since it probably saves the user some time.
The general format of a component's definition is:
<definition> ::= (<type> <name> [:host <host>] [:device <device>] [:source-pathname <pathname>] [:source-extension <extension>] [:binary-pathname <pathname>] [:binary-extension <extension>] [:package <package>] [:initially-do <form>] [:finally-do <form>] [:components (:serial <definition>*)|(<definition>*)] [:depends-on (<name>*)] [:compile-form <form>] [:load-form <form>]) <type> ::= :system | :module | :file <def-or-fn> ::= <definition> | <pathname>
I modified the above to reflect the addition of the
:serial keyword in
:components and also to reflect the fact that "naked" filenames seem to be
:file type modules do not admit of adding a
option, nor do they properly handle absolute file names. Unfortunately, there doesn't seem
to be any code that will barf if you give a bad option.
The toplevel defsystem form substitutes defsystem for :system.
The function operate-on-system is used to compile or load a system, or do any other operation on a system. At present only compile and load operations are defined, but other operations such as edit, hardcopy, or applying arbitrary functions (e.g., enscript, lpr) to every file in the system could be added easily.
The syntax of operate-on-system is as follows:
operate-on-system system-name operation &key force test verbose dribble load-source-instead-of-binary load-source-if-no-binary bother-user-if-no-binary
An implicit assumption is that if we need to load a file for some reason, then we should be able to compile it immediately before we need to load it. This obviates the need to specify separate load and compile dependencies in the modules.
Files which must not be compiled should be loaded in the initializations or finalizations of a module by means of an explicit load form.
Note that under this assumption, the example given in the PCL defsystem becomes quite ludicrous. Those constraints are of the form:
When you add in the reasonable assumption that before you load C, you must compile C, you get a cycle.
The only case is which this might not be true is in a system which worked on the dependency graph of individual definitions. But we have restricted ourselves to file dependencies and will stick with that. (In situations where a file defining macros must have the sources loaded before compiling them, most often it is because the macros are used before they are defined, and hence assumed to be functions. This can be fixed by organizing the macros better, or including them in a separate file.)
To define a new operation, write a function with parameters component and force that performs the operation. The function component-pathname may be used to extract the source and binary pathnames from the component. [Component-pathname takes parameters component and file-type, where file-type is either :source or :binary, and returns the appropriate pathname.] If the component has "changed" as a result of the operation, T should be returned; otherwise nil. See the definition of compile-file-operation and load-file-operation for examples.
Then install the definition using component-operation, which takes as parameters the symbol which will be used to name the operation in operate-on-system, and the name of the function. For example, here's the definition of the 'compile and :compile operations:
(component-operation :compile 'compile-and-load-operation) (component-operation 'compile 'compile-and-load-operation)
Eventually this system will include portable definitions of 'hardcopy and 'edit.
This defsystem interacts smoothly with the require and provide facilities of Common Lisp. Operate-on-system automatically provides the name of any system it loads, and uses the new definition of require to load any dependencies of the toplevel system.
To facilitate this, three new optional arguments have been added to require. Thus the new syntax of require is as follows:
require system-name &optional pathname definition-pname default-action version
If pathname is provided, the new require behaves just like the old definition. Otherwise it first tries to find the definition of the system-name (if it is not already defined it will load the definition file if it is in the current-directory, the central-registry directory, or the directory specified by definition-pname) and runs operate-on-system on the system definition. If no definition is to be found, it will evaluate the default-action if there is one. Otherwise it will try running the old definition of require on just the system name. If all else fails, it will print out a warning.
Here's a system definition for the files in the following directory structure:
% du -a test 1 test/fancy/macros.lisp 1 test/fancy/primitives.lisp 3 test/fancy 1 test/macros.lisp 1 test/primitives.lisp 1 test/graphics/macros.lisp 1 test/graphics/primitives.lisp 3 test/graphics 1 test/os/macros.lisp 1 test/os/primitives.lisp 3 test/os 12 test (defsystem test :source-pathname "/afs/cs.cmu.edu/user/mkant/Defsystem/test/" :source-extension "lisp" :binary-pathname nil :binary-extension nil :components ((:module basic :source-pathname "" :components ((:file "primitives") (:file "macros" :depends-on ("primitives")))) (:module graphics :source-pathname "graphics" :components ((:file "macros" :depends-on ("primitives")) (:file "primitives")) :depends-on (basic)) (:module fancy-stuff :source-pathname "fancy" :components ((:file "macros" :depends-on ("primitives")) (:file "primitives")) :depends-on (graphics operating-system)) (:module operating-system :source-pathname "os" :components ((:file "primitives") (:file "macros" :depends-on ("primitives"))) :depends-on (basic))) :depends-on nil) <cl> (operate-on-system 'test 'compile :verbose t) ; - Compiling system "test" ; - Compiling module "basic" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/primitives.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/primitives.fasl" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/macros.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/macros.fasl" ; - Compiling module "graphics" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/graphics/primitives.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/graphics/primitives.fasl" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/graphics/macros.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/graphics/macros.fasl" ; - Compiling module "operating-system" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/os/primitives.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/os/primitives.fasl" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/os/macros.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/os/macros.fasl" ; - Compiling module "fancy-stuff" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/fancy/primitives.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/fancy/primitives.fasl" ; - Compiling source file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/fancy/macros.lisp" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/fancy/macros.fasl" ; - Providing system test NIL <cl> (operate-on-system 'test 'load :verbose t) ; - Loading system "test" ; - Loading module "basic" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/primitives.fasl" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/macros.fasl" ; - Loading module "graphics" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/graphics/primitives.fasl" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/graphics/macros.fasl" ; - Loading module "operating-system" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/os/primitives.fasl" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/os/macros.fasl" ; - Loading module "fancy-stuff" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/fancy/primitives.fasl" ; - Loading binary file ; "/afs/cs.cmu.edu/user/mkant/Defsystem/test/fancy/macros.fasl" ; - Providing system test NIL
Sometimes one wishes to build system definitions that rely on external systems, defined elsewhere. To do this, one must reference those external systems only as dependencies on the top-level system. Components cannot reference external systems as dependencies.
Should have example here.
You can also load foreign files with defsystem. For example, to define that C components are compiled by calling out to "make" and loaded using the foreign loader, try something like this example (originally from db-sockets):
(defparameter *make-program* "make") (defun c-make-file (filename &rest args &key output-file error-file) ;; make foo.o (declare (ignore args error-file)) (make::run-unix-program *make-program* (list output-file))) (make:define-language :c :compiler #'c-make-file :loader #+:lucid #'load-foreign-files #+cmu #'alien::load-foreign #+sbcl #'sb-alien::load-foreign #+:allegro #'load #-(or :cmu :sbcl :lucid :allegro) #'load :source-extension "c" :binary-extension "o")
then you define the relevant component like this:
(:file "get_h_errno.c" :language :c :source-extension "c" :binary-extension "o")
Macintosh pathnames are not fully supported at this time because of irregularities in the Allegro Common Lisp definition of the pathname functions. Thus system definitions will not be portable to the Macintosh. To convert them, include the device in the toplevel pathname and include trailing colons in the pathnames of each module.
We currently assume that compilation-load dependencies and if-changed dependencies are identical. However, in some cases this might not be true. For example, if we change a macro we have to recompile functions that depend on it, but not if we change a function. Splitting these apart (with appropriate defaulting) would be nice, but not worth doing immediately since it may save only a couple of file recompilations, while making the defsystem much more complex. And if someone has such a large system that this matters, they've got more important problems.