Ignore:
Timestamp:
03/25/14 09:04:23 (3 years ago)
Author:
mevenson
Message:

Update to ASDF 3.1.0.103.

Seems to fix loading of Ironclad, and other Quicklisp failures.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/abcl/doc/asdf/asdf.texinfo

    r14636 r14661  
    247247(In the context of compatibility requirements,
    248248ASDF 2.27, released on Feb 1st 2013, and further 2.x releases up to 2.33,
    249 count as pre-releases of ASDF 3, and define the :asdf3 feature;
     249count as pre-releases of ASDF 3, and define the @code{:asdf3} feature;
    250250still, please use the latest release).
     251Release ASDF 3.1.1 and later also define the @code{:asdf3.1} feature.
    251252
    252253Also note that ASDF is not to be confused with ASDF-Install.
     
    257258If you want to download software from version control instead of tarballs,
    258259so you may more easily modify it, we recommend clbuild.
     260We recommend @file{~/common-lisp/}
     261as a place into which to install Common Lisp software;
     262starting with ASDF 3.1.1, it is included in the default source-registry configuration.
    259263
    260264@node  Quick start summary, Loading ASDF, Introduction, Top
     
    277281For more details, @xref{Configuring ASDF to find your systems}.
    278282The simplest way is simply to put all your lisp code in subdirectories of
    279 @file{~/.local/share/common-lisp/source/}.
     283@file{~/common-lisp/} (starting with ASDF 3.1.1),
     284or @file{~/.local/share/common-lisp/source/}
     285(for ASDF 2 and later, or if you want to keep source in a hidden directory).
    280286Such code will automatically be found.
    281287
     
    434440Still, the ASDF source repository contains a script
    435441@file{bin/install-asdf-as-module} that can help you do that.
    436 It relies on cl-launch 4 for command-line invocation,
     442It relies on @file{cl-launch} 4 for command-line invocation,
    437443which may depend on ASDF being checked out in @file{~/cl/asdf/}
    438444if your implementation doesn't even have an ASDF 2;
    439 but you can run the code it manually if needs be.
     445but if you don't have @file{cl-launch},
     446you can instead @code{(load "bin/install-asdf-as-module")}
     447from your implementation's REPL.
    440448
    441449Finally, if your implementation only provides ASDF 2,
     
    554562@end menu
    555563
    556 @node Configuring ASDF to find your systems, Configuring where ASDF stores object files, Configuring ASDF, Configuring ASDF
     564@node Configuring ASDF to find your systems, Configuring ASDF to find your systems --- old style, Configuring ASDF, Configuring ASDF
    557565@section Configuring ASDF to find your systems
    558566
     
    567575@item
    568576Put all of your systems in subdirectories of
     577@file{~/common-lisp/} or
    569578@file{~/.local/share/common-lisp/source/}.
    570 If you install software there (it can be a symlink),
    571 you don't need further configuration.
     579If you install software there, you don't need further configuration.
     580(NB: @file{~/common-lisp/} is only included in the default configuration
     581starting with ASDF 3.1.1 or later)
    572582
    573583@item
     
    615625(asdf:clear-source-registry)
    616626@end lisp
    617 
    618 @c FIXME: too specific.  Push this down to discussion of dumping an
    619 @c image?
    620 
    621 @c And you probably should do so before you dump your Lisp image,
    622 @c if the configuration may change
    623 @c between the machine where you save it at the time you save it
    624 @c and the machine you resume it at the time you resume it.
    625 @c Actually, you should use @code{(asdf:clear-configuration)}
    626 @c before you dump your Lisp image, which includes the above.
    627627
    628628@item
     
    732732
    733733
    734 @node Configuring where ASDF stores object files,  , Configuring ASDF to find your systems, Configuring ASDF
     734@node Configuring where ASDF stores object files, Resetting the ASDF configuration, Configuring ASDF to find your systems --- old style, Configuring ASDF
    735735@section Configuring where ASDF stores object files
    736736@findex clear-output-translations
     
    829829@end defun
    830830
    831 If you use SBCL, CMUCL or SCL, you may use this snippet
    832 so that the ASDF configuration be cleared automatically as you dump an image:
    833 
    834 @example
    835 #+(or cmu sbcl scl)
    836 (pushnew 'clear-configuration
    837          #+(or cmu scl) ext:*before-save-initializations*
    838          #+sbcl sb-ext:*save-hooks*)
    839 @end example
    840 
    841 For compatibility with all Lisp implementations, however,
    842 you might want instead your build script to explicitly call
    843 @code{(asdf:clear-configuration)} at an appropriate moment before dumping.
     831This function is pushed onto the @code{uiop:*image-dump-hook*} by default,
     832which means that if you save an image using @code{uiop:dump-image},
     833or via @code{asdf:image-op} and @code{asdf:program-op},
     834it will be automatically called to clear your configuration.
     835If for some reason you prefer to call your implementation's underlying functionality,
     836be sure to call @code{clear-configuration} manually,
     837or push it into your implementation's equivalent of @code{uiop:*image-dump-hook*},
     838e.g. @code{sb-ext:*save-hooks*} on SBCL, or @code{ext:*before-save-initializations*}
     839on CMUCL and SCL, etc.
    844840
    845841@node  Using ASDF, Defining systems with defsystem, Configuring ASDF, Top
Note: See TracChangeset for help on using the changeset viewer.