Commit 81429606 authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

A FAQ, plus Makefile cleanups.

parent 8f30008c
......@@ -38,7 +38,7 @@ website-copy: FORCE
bin/rsync-cp.sh tmp/asdf.lisp $(webhome_private)
clean_dirs = $(sourceDirectory)
clean_extensions = fasl dfsl cfsl fasl fas lib dx32fsl lx64fsl lx32fsl
clean_extensions = fasl dfsl cfsl fasl fas lib dx32fsl lx64fsl lx32fsl o
clean: FORCE
@for dir in $(clean_dirs); do \
......@@ -63,4 +63,4 @@ test-all: FORCE
sbcl --userinit /dev/null --sysinit /dev/null --load bin/make-helper.lisp \
--eval "(write-test-web-pages)" --eval "(quit)"
FORCE:
\ No newline at end of file
FORCE:
......@@ -14,7 +14,7 @@
This manual describes asdf, a system definition facility for Common
Lisp programs and libraries.
asdf Copyright @copyright{} 2001-2007 Daniel Barlow and contributors
asdf Copyright @copyright{} 2001-2010 Daniel Barlow and contributors
This manual Copyright @copyright{} 2001-2007 Daniel Barlow and
contributors
......@@ -1282,8 +1282,6 @@ location of the system's source file and the relative pathname. For example
@comment node-name, next, previous, up
@chapter Getting the latest version
@emph{FIXME: Need to revise this to give information about the git repository.}
Decide which version you want. HEAD is the newest version and
usually OK, whereas RELEASE is for cautious people (e.g. who already
have systems using asdf that they don't want broken), a slightly older
......@@ -1396,6 +1394,51 @@ interfere.
ASDF bugs are tracked on launchpad: @url{https://launchpad.net/asdf}.
@item ``I want to put my module's files at the top level. How do I do this?''
By default, the files contained in an asdf module go in a subdirectory
with the same name as the module. However, this can be overridden by
adding a @code{:pathname} argument to the module description. For
example, here is how it is done in the spatial-trees ASDF system
definition:
@example
(asdf:defsystem :spatial-trees
:components
((:module base
:pathname #.(make-pathname :directory '(:relative))
:components
((:file "package")
(:file "basedefs" :depends-on ("package"))
(:file "rectangles" :depends-on ("package"))))
(:module tree-impls
:depends-on (base)
:pathname #.(make-pathname :directory '(:relative))
:components
((:file "r-trees")
(:file "greene-trees" :depends-on ("r-trees"))
(:file "rstar-trees" :depends-on ("r-trees"))
(:file "rplus-trees" :depends-on ("r-trees"))
(:file "x-trees" :depends-on ("r-trees" "rstar-trees"))))
(:module viz
:depends-on (base)
:pathname #.(make-pathname :directory '(:relative))
:components
((:static-file "spatial-tree-viz"
:pathname #p"spatial-tree-viz.lisp")))
(:module tests
:depends-on (base)
:pathname #.(make-pathname :directory '(:relative))
:components
((:static-file "spatial-tree-test"
:pathname #p"spatial-tree-test.lisp")))
(:static-file "LICENCE")
(:static-file "TODO")))
@end example
All of the files in the @code{tree-impls} module are at the top level,
instead of in a @code{tree-impls/} subdirectory.
@end itemize
@node TODO list, missing bits in implementation, FAQ, Top
......@@ -1612,4 +1655,3 @@ probably will be again soon ]
@bye
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment