Commit 092fa218 authored by Francois-Rene Rideau's avatar Francois-Rene Rideau

Merge branch 'master' into minimakefile

parents bbc13614 8366db2e
......@@ -258,7 +258,7 @@ Issues with using and extending ASDF to define systems
ASDF development FAQs
* How do run the tests interactively in a REPL?::
* How do I run the tests interactively in a REPL?::
@end detailmenu
@end menu
......@@ -1112,7 +1112,10 @@ Only period-separated non-negative integers are accepted at present.
See below Version specifiers in @ref{The defsystem grammar}.
@item
This file contains a single @code{defsystem} declaration.
This file contains a single form, the @code{defsystem} declaration.
No @code{in-package} form, no @code{asdf:} package prefix, no nothing.
Just the one naked @code{defsystem} form.
This is what we recommend.
More complex system definition files are possible with arbitrary Lisp code,
but we recommend that you keep it simple if you can.
This will make your system definitions more robust and more future-proof.
......@@ -4959,7 +4962,6 @@ plus many implementations that previously did not.
ASDF has been made to work with all actively maintained CL
implementations and even a few implementations that are @emph{not}
actively maintained.
@xref{FAQ,,``What has changed between ASDF 1 ASDF 2 and ASDF 3?''}.
Furthermore, it is possible to upgrade from ASDF 1 to ASDF 2 or ASDF 3 on the fly
(though we recommend instead upgrading your implementation or replacing its ASDF module).
......@@ -5461,12 +5463,12 @@ or the code of @url{https://cliki.net/cl-launch,@code{cl-launch}}.
Note that in addition to the pitfalls and constraints above,
these heroic scripts (should you wish to write or modify one),
must take care to configure ASDF @emph{twice}.
One first time, right after you load the old ASDF 2 and before you upgrade to the new ASDF 3,
A first time, right after you load the old ASDF 2 and before you upgrade to the new ASDF 3,
so it may find where you put ASDF 3.
One second time, because some implementations can't handle a smooth upgrade to ASDF 3,
A second time, because some implementations can't handle a smooth upgrade to ASDF 3,
and lose configuration as they do.
@lisp
(require "asdf")
(ignore-errors (funcall 'require "asdf")) ;; <--- try real hard
;; <--- insert heroics here, if that failed to provide ASDF 2 or 3
;; <--- insert configuration here, if that succeeded
(asdf:load-system "asdf")
......@@ -5495,7 +5497,6 @@ and lose configuration as they do.
@code{asdf-ecl} and its short-lived successor @code{asdf-bundle} are no more,
having been replaced by code now built into ASDF 3.
Moreover, the name of the bundle operations has changed since ASDF 3.1.3.
@xref{What happened to the bundle operations}.
And yet, the feature is not enabled to be used by @code{load-system} by default on ECL as originally intended,
because of a bug in ECL itself found during testing.
......@@ -5990,11 +5991,11 @@ Use from the @code{named-readtables} system the macro @code{named-readtables:def
@section ASDF development FAQs
@menu
* How do run the tests interactively in a REPL?::
* How do I run the tests interactively in a REPL?::
@end menu
@node How do run the tests interactively in a REPL?, , ASDF development FAQs, ASDF development FAQs
@subsection How do run the tests interactively in a REPL?
@node How do I run the tests interactively in a REPL?, , ASDF development FAQs, ASDF development FAQs
@subsection How do I run the tests interactively in a REPL?
This not-so-frequently asked question is primarily for ASDF developers,
but those who encounter an unexpected error in some test may be
......
......@@ -37,14 +37,14 @@
extensibility, configurability, internal consistency,
and the ability to deliver standalone executables.
Its notable versions include pre-release 2.27 on February 1st 2013,
first release 3.0.0 on May 15th 2013,
first stable release 3.0.1 on May 16th 2013,
major release 3.1.2 on May 6th 2014,
and latest release 3.1.4 on October 10th 2014.
and latest release 3.1.5 on July 21st 2015.
</p>
<a id="what_it_is"></a>
<h3>What it is</h3>
<p>ASDF stands for <em>A</em>nother <em>S</em>ystem <em>D</em>efinition <em>F</em>acility,
in the continuity of the Lisp <tt>DEFSYSTEM</tt> of yore.
the successor of the Lisp <tt>DEFSYSTEM</tt> of yore.
</p>
<p>ASDF 3 contains two parts: <tt>asdf/defsystem</tt> and <tt>uiop</tt>.
</p>
......@@ -60,7 +60,7 @@
And you must typically compile and load files that define packages, macros, variables,
before you may compile and load other files that use them.
</p>
<p>It is roughly what Common Lisp hackers use to build and load software
<p>ASDF is what Common Lisp hackers use to build and load software,
where C hackers might use GNU <tt>Make</tt> to build software and
<tt>ld.so</tt> to load it.
</p>
......@@ -88,7 +88,7 @@
and the documentation as extracted from its docstrings by
<a href="http://bimib.disco.unimib.it/people/Marco.Antoniotti/Projects/CL/HELAMBDAP/tests/asdf-uiop/docs/html/dictionary/dictionary.html">HEΛP</a>
(beware: you can, though it's not obvious, scroll the list of packages
with a scroll the right of the top-left pane, and then click on the one
with a scrollbar on the right of the top-left pane, and then click on the package
you're interested in to browse its symbols).
</p>
<p><tt>uiop</tt> is distributed as part of the <tt>ASDF</tt>,
......@@ -223,6 +223,8 @@ MKCL <jean.claude.beaudoin@gmail.com>,
SBCL <sbcl-devel@lists.sourceforge.net>,
Scieneer CL (Douglas Crosher) <dtc3@scieneer.com>,
XCL (Peter Graves) <gnooth@gmail.com>
CLASP <clasp-devel@common-lisp.net>
Corman Common Lisp <admin@cormanlisp.com>
-->
<p>
If there is an old or new implementation that we are missing,
......@@ -310,6 +312,10 @@ XCL (Peter Graves) <gnooth@gmail.com>
<h3>Extensions</h3>
<p>Known extensions to ASDF include:</p>
<ul>
<li>
<a href="https://gitlab.common-lisp.net/xcvb/asdf-dependency-grovel">
<tt>asdf-dependency-grovel</tt></a>,
to compute the actual dependencies in a big ASDF system.</li>
<li><a href="https://gitlab.common-lisp.net/asdf/asdf-encodings"
><tt>asdf-encodings</tt></a>,
to compile Lisp source files with character encodings other than UTF-8.</li>
......@@ -317,20 +323,22 @@ XCL (Peter Graves) <gnooth@gmail.com>
><tt>asdf-finalizers</tt></a>,
to allow macros to include code to be evaluated
at the end of a file being compiled.</li>
<li>
<a href="https://gitlab.common-lisp.net/xcvb/asdf-dependency-grovel">
<tt>asdf-dependency-grovel</tt></a>,
to compute the actual dependencies in a big ASDF system.</li>
<li><a href="https://common-lisp.net/project/qitab/"
><tt>poiu</tt></a>,
to compile a system in parallel on a multiprocessor machine.</li>
<li><a href="http://www.lrde.epita.fr/~didier/software/lisp/misc.php#asdf-flv"
><tt>asdf-flv</tt></a>,
to bind file-local variables around the compilation of some files.</li>
<li><a href="https://common-lisp.net/project/asdf-system-connections/"
><tt>asdf-system-connections</tt></a>,
lets you specify systems that are automatically loaded when
two other systems are loaded, to connect them.</li>
<li><a href="http://www.lrde.epita.fr/~didier/software/lisp/misc.php#asdf-flv"
><tt>asdf-flv</tt></a>,
to bind file-local variables around the compilation of some files.</li>
<li><a href="https://common-lisp.net/project/cffi/"
><tt>cffi</tt></a>,
lets you interface between with functions and datastructures written in C
and functions written in Lisp,
including support for automatically detecting constants from C macros,
linking to dynamic libraries, and writing your own wrapper code in C.</li>
<li><a href="https://common-lisp.net/project/qitab/"
><tt>poiu</tt></a>,
to compile a system in parallel on a multiprocessor machine.</li>
</ul>
<p>Former extensions, now superseded, include:</p>
<ul>
......@@ -423,14 +431,19 @@ XCL (Peter Graves) <gnooth@gmail.com>
<a id="news"></a>
<h3>What is happening</h3>
<dl>
<dt>July 2015</dt>
<dd>An extensive bout of bug-fixing, notably on Windows, leads to
release of ASDF 3.1.5 on 21 July 2015. XDG handling has been improved to
be more compliant with the standard. <em>Preliminary</em> support for
immutable systems has been added.</dd>
<dt>May 2015</dt>
<dd>With the LispWorks 7.0 release, all actively maintained CL implementations
are now providind ASDF 3.0 or later, and
are now providing ASDF 3.0 or later, and
support for older variants is now officially dropped.</dd>
<dt>October 2014</dt>
<dd>More bug fixing leads to release of 3.1.4 on 10 October 2014.
There should be no incompatibilities. See the <a
href="changelog">Changelog</a> for more details.</dd>
There should be no incompatibilities.
See the <a href="changelog">Changelog</a> for more details.</dd>
<dt>August 2014</dt>
<dd>The ASDF mailing lists have been reestablished, in particular
asdf-announce, which should allow CL implementers better access to only
......@@ -505,7 +518,7 @@ XCL (Peter Graves) <gnooth@gmail.com>
<a class="nav" href="http://common-lisp.net/" title="Common-Lisp.net"> <img src="http://common-lisp.net/project/cl-containers/shared/buttons/lisp-lizard.png" width="80" height="15" title="Common-Lisp.net" alt="Common-Lisp.net button" /></a>
<p><span class="copyright"Copyright &copy; 2001-2015 Daniel Barlow and contributors</span></p>
<p>ASDF has an <a href="http://www.opensource.org/licenses/mit-license.php">MIT style</a> license</p>
<div id="timestamp">Last updated 2015-05-05</div>
<div id="timestamp">Last updated 2015-07-21</div>
</div>
</body>
</html>
This diff is collapsed.
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