120 lines
5.7 KiB
HTML
120 lines
5.7 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>ASDF can portably name files in subdirectories (ASDF Manual)</title>
|
||
|
|
|
||
|
|
<meta name="description" content="ASDF can portably name files in subdirectories (ASDF Manual)">
|
||
|
|
<meta name="keywords" content="ASDF can portably name files in subdirectories (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="Output-translations.html" rel="next" title="Output translations">
|
||
|
|
<link href="How-do-I-detect-the-ASDF-version_003f.html" rel="prev" title="How do I detect the ASDF version?">
|
||
|
|
<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="ASDF-can-portably-name-files-in-subdirectories">
|
||
|
|
<div class="header">
|
||
|
|
<p>
|
||
|
|
Next: <a href="Output-translations.html" accesskey="n" rel="next">Output translations</a>, Previous: <a href="How-do-I-detect-the-ASDF-version_003f.html" accesskey="p" rel="prev">How do I detect the ASDF version?</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="ASDF-can-portably-name-files-in-subdirectories-1"></span><h4 class="subsection">13.3.3 ASDF can portably name files in subdirectories</h4>
|
||
|
|
|
||
|
|
<p>Common Lisp namestrings are not portable,
|
||
|
|
except maybe for logical pathname namestrings,
|
||
|
|
that themselves have various limitations and require a lot of setup
|
||
|
|
that is itself ultimately non-portable.
|
||
|
|
</p>
|
||
|
|
<p>In ASDF 1, the only portable ways to refer to pathnames inside systems and components
|
||
|
|
were very awkward, using <code>#.(make-pathname ...)</code> and
|
||
|
|
<code>#.(merge-pathnames ...)</code>.
|
||
|
|
Even the above were themselves were inadequate in the general case
|
||
|
|
due to host and device issues, unless horribly complex patterns were used.
|
||
|
|
Plenty of simple cases that looked portable actually weren’t,
|
||
|
|
leading to much confusion and greavance.
|
||
|
|
</p>
|
||
|
|
<p>ASDF 2 implements its own portable syntax for strings as pathname specifiers.
|
||
|
|
Naming files within a system definition becomes easy and portable again.
|
||
|
|
See <a href="Miscellaneous-additional-functionality.html">system-relative-pathname</a>,
|
||
|
|
<code>merge-pathnames*</code>,
|
||
|
|
<code>coerce-pathname</code>.
|
||
|
|
</p>
|
||
|
|
<p>On the other hand, there are places where systems used to accept namestrings
|
||
|
|
where you must now use an explicit pathname object:
|
||
|
|
<code>(defsystem ... :pathname "LOGICAL-HOST:PATH;TO;SYSTEM;" ...)</code>
|
||
|
|
must now be written with the <code>#p</code> syntax:
|
||
|
|
<code>(defsystem ... :pathname #p"LOGICAL-HOST:PATH;TO;SYSTEM;" ...)</code>.
|
||
|
|
We recommend against using pathname objects in general and logical pathnames in particular.
|
||
|
|
Your code will be much more portable using ASDF’s pathname specifiers.
|
||
|
|
</p>
|
||
|
|
<p>See <a href="The-defsystem-grammar.html#Pathname-specifiers">Pathname specifiers</a>.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|