181 lines
8.8 KiB
HTML
181 lines
8.8 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
|
<html>
|
|
<!-- Created by GNU Texinfo 6.8, https://www.gnu.org/software/texinfo/ -->
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<!-- This manual describes ASDF, a system definition facility
|
|
for Common Lisp programs and libraries.
|
|
|
|
You can find the latest version of this manual at
|
|
https://common-lisp.net/project/asdf/asdf.html.
|
|
|
|
ASDF Copyright (C) 2001-2019 Daniel Barlow and contributors.
|
|
|
|
This manual Copyright (C) 2001-2019 Daniel Barlow and contributors.
|
|
|
|
This manual revised (C) 2009-2019 Robert P. Goldman and Francois-Rene Rideau.
|
|
|
|
Permission is hereby granted, free of charge, to any person obtaining
|
|
a copy of this software and associated documentation files (the
|
|
"Software"), to deal in the Software without restriction, including
|
|
without limitation the rights to use, copy, modify, merge, publish,
|
|
distribute, sublicense, and/or sell copies of the Software, and to
|
|
permit persons to whom the Software is furnished to do so, subject to
|
|
the following conditions:
|
|
|
|
The above copyright notice and this permission notice shall be
|
|
included in all copies or substantial portions of the Software.
|
|
|
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
|
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
|
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
|
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
|
|
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
|
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
|
|
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
-->
|
|
<title>Pitfalls of the transition to ASDF 2 (ASDF Manual)</title>
|
|
|
|
<meta name="description" content="Pitfalls of the transition to ASDF 2 (ASDF Manual)">
|
|
<meta name="keywords" content="Pitfalls of the transition to ASDF 2 (ASDF Manual)">
|
|
<meta name="resource-type" content="document">
|
|
<meta name="distribution" content="global">
|
|
<meta name="Generator" content="makeinfo">
|
|
<meta name="viewport" content="width=device-width,initial-scale=1">
|
|
|
|
<link href="index.html" rel="start" title="Top">
|
|
<link href="Concept-Index.html" rel="index" title="Concept Index">
|
|
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
|
|
<link href="What-has-changed-between-ASDF-1-ASDF-2-and-ASDF-3_003f.html" rel="up" title="What has changed between ASDF 1 ASDF 2 and ASDF 3?">
|
|
<link href="Pitfalls-of-the-upgrade-to-ASDF-3.html" rel="next" title="Pitfalls of the upgrade to ASDF 3">
|
|
<link href="Decoupled-release-cycle.html" rel="prev" title="Decoupled release cycle">
|
|
<style type="text/css">
|
|
<!--
|
|
a.copiable-anchor {visibility: hidden; text-decoration: none; line-height: 0em}
|
|
a.summary-letter {text-decoration: none}
|
|
blockquote.indentedblock {margin-right: 0em}
|
|
div.display {margin-left: 3.2em}
|
|
div.example {margin-left: 3.2em}
|
|
kbd {font-style: oblique}
|
|
pre.display {font-family: inherit}
|
|
pre.format {font-family: inherit}
|
|
pre.menu-comment {font-family: serif}
|
|
pre.menu-preformatted {font-family: serif}
|
|
span.nolinebreak {white-space: nowrap}
|
|
span.roman {font-family: initial; font-weight: normal}
|
|
span.sansserif {font-family: sans-serif; font-weight: normal}
|
|
span:hover a.copiable-anchor {visibility: visible}
|
|
ul.no-bullet {list-style: none}
|
|
-->
|
|
</style>
|
|
|
|
|
|
</head>
|
|
|
|
<body lang="en">
|
|
<div class="subsection" id="Pitfalls-of-the-transition-to-ASDF-2">
|
|
<div class="header">
|
|
<p>
|
|
Next: <a href="Pitfalls-of-the-upgrade-to-ASDF-3.html" accesskey="n" rel="next">Pitfalls of the upgrade to ASDF 3</a>, Previous: <a href="Decoupled-release-cycle.html" accesskey="p" rel="prev">Decoupled release cycle</a>, Up: <a href="What-has-changed-between-ASDF-1-ASDF-2-and-ASDF-3_003f.html" accesskey="u" rel="up">“What has changed between ASDF 1, ASDF 2, and ASDF 3?”</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
|
|
</div>
|
|
<hr>
|
|
<span id="Pitfalls-of-the-transition-to-ASDF-2-1"></span><h4 class="subsection">13.3.11 Pitfalls of the transition to ASDF 2</h4>
|
|
|
|
<p>The main pitfalls in upgrading to ASDF 2 seem to be related
|
|
to the output translation mechanism.
|
|
</p>
|
|
<ul>
|
|
<li> Output translations is enabled by default. This may surprise some users,
|
|
most of them in pleasant way (we hope), a few of them in an unpleasant way.
|
|
It is trivial to disable output translations.
|
|
See <a href="FAQ.html">“How can I wholly disable the compiler output cache?”</a>.
|
|
|
|
</li><li> Some systems in the large have been known
|
|
not to play well with output translations.
|
|
They were relatively easy to fix.
|
|
Once again, it is also easy to disable output translations,
|
|
or to override its configuration.
|
|
|
|
</li><li> The new ASDF output translations are incompatible with ASDF-Binary-Locations.
|
|
They replace A-B-L, and there is compatibility mode to emulate
|
|
your previous A-B-L configuration.
|
|
See <code>enable-asdf-binary-locations-compatibility</code> in
|
|
see <a href="Controlling-where-ASDF-saves-compiled-files.html">Backward Compatibility</a>.
|
|
But thou shalt not load ABL on top of ASDF 2.
|
|
|
|
</li></ul>
|
|
|
|
<p>Other issues include the following:
|
|
</p>
|
|
<ul>
|
|
<li> ASDF pathname designators are now specified
|
|
in places where they were unspecified,
|
|
and a few small adjustments have to be made to some non-portable defsystems.
|
|
Notably, in the <code>:pathname</code> argument
|
|
to a <code>defsystem</code> and its components,
|
|
a logical pathname (or implementation-dependent hierarchical pathname)
|
|
must now be specified with <code>#p</code> syntax
|
|
where the namestring might have previously sufficed;
|
|
moreover when evaluation is desired <code>#.</code> must be used,
|
|
where it wasn’t necessary in the toplevel <code>:pathname</code> argument
|
|
(but necessary in other <code>:pathname</code> arguments).
|
|
|
|
</li><li> There is a slight performance bug, notably on SBCL,
|
|
when initially searching for <samp>asd</samp> files,
|
|
the implicit <code>(directory "/configured/path/**/*.asd")</code>
|
|
for every configured path <code>(:tree "/configured/path/")</code>
|
|
in your <code>source-registry</code> configuration can cause a slight pause.
|
|
Try to <code>(time (asdf:initialize-source-registry))</code>
|
|
to see how bad it is or isn’t on your system.
|
|
If you insist on not having this pause,
|
|
you can avoid the pause by overriding the default source-registry configuration
|
|
and not use any deep <code>:tree</code> entry but only <code>:directory</code> entries
|
|
or shallow <code>:tree</code> entries.
|
|
Or you can fix your implementation to not be quite that slow
|
|
when recursing through directories.
|
|
<em>Update</em>: This performance bug fixed the hard way in 2.010.
|
|
|
|
</li><li> On Windows, only LispWorks supports proper default configuration pathnames
|
|
based on the Windows registry.
|
|
Other implementations make do with environment variables,
|
|
that you may have to define yourself
|
|
if you’re using an older version of Windows.
|
|
Windows support is somewhat less tested than Unix support.
|
|
Please help report and fix bugs.
|
|
<em>Update</em>: As of ASDF 2.21, all implementations
|
|
should now use the same proper default configuration pathnames
|
|
and they should actually work, though they haven’t all been tested.
|
|
|
|
</li><li> The mechanism by which one customizes a system so that Lisp files
|
|
may use a different extension from the default <samp>.lisp</samp> has changed.
|
|
Previously, the pathname for a component
|
|
was lazily computed when operating on a system,
|
|
and you would
|
|
<code>(defmethod source-file-type ((component cl-source-file) (system (eql (find-system 'foo))))
|
|
(declare (ignorable component system)) "lis")</code>.
|
|
Now, the pathname for a component is eagerly computed when defining the system,
|
|
and instead you will <code>(defclass cl-source-file.lis (cl-source-file) ((type :initform "lis")))</code>
|
|
and use <code>:default-component-class cl-source-file.lis</code>
|
|
as argument to <code>defsystem</code>,
|
|
as detailed in a see <a href="FAQ.html">How do I create a system definition where all the source files have a .cl extension?</a> below.
|
|
<code>source-file-type</code> is deprecated. To access a component’s
|
|
file-type, use <code>file-type</code>, instead. <code>source-file-type</code> will
|
|
be removed.
|
|
|
|
<span id="index-source_002dfile_002dtype"></span>
|
|
<span id="index-file_002dtype"></span>
|
|
|
|
</li></ul>
|
|
|
|
|
|
</div>
|
|
<hr>
|
|
<div class="header">
|
|
<p>
|
|
Next: <a href="Pitfalls-of-the-upgrade-to-ASDF-3.html">Pitfalls of the upgrade to ASDF 3</a>, Previous: <a href="Decoupled-release-cycle.html">Decoupled release cycle</a>, Up: <a href="What-has-changed-between-ASDF-1-ASDF-2-and-ASDF-3_003f.html">“What has changed between ASDF 1, ASDF 2, and ASDF 3?”</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
|
|
</div>
|
|
|
|
|
|
|
|
</body>
|
|
</html>
|