1
0
Fork 0
cl-sites/asdf.common-lisp.dev/asdf/LOAD_002dPATHNAME-has-a-weird-value.html
2023-11-12 11:34:18 +01:00

115 lines
5.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>LOAD-PATHNAME has a weird value (ASDF Manual)</title>
<meta name="description" content="LOAD-PATHNAME has a weird value (ASDF Manual)">
<meta name="keywords" content="LOAD-PATHNAME has a weird value (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="Issues-with-using-and-extending-ASDF-to-define-systems.html" rel="up" title="Issues with using and extending ASDF to define systems">
<link href="How-can-I-produce-a-binary-at-a-specific-path-from-sources-at-a-specific-path.html" rel="next" title="How can I produce a binary at a specific path from sources at a specific path">
<link href="How-can-I-capture-ASDF_0027s-output_003f.html" rel="prev" title="How can I capture ASDF's output?">
<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="LOAD_002dPATHNAME-has-a-weird-value">
<div class="header">
<p>
Next: <a href="How-can-I-produce-a-binary-at-a-specific-path-from-sources-at-a-specific-path.html" accesskey="n" rel="next">How can I produce a binary at a specific path from sources at a specific path?</a>, Previous: <a href="How-can-I-capture-ASDF_0027s-output_003f.html" accesskey="p" rel="prev">How can I capture ASDF&rsquo;s output?</a>, Up: <a href="Issues-with-using-and-extending-ASDF-to-define-systems.html" accesskey="u" rel="up">Issues with using and extending ASDF to define systems</a> &nbsp; [<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="g_t_002aLOAD_002dPATHNAME_002a-and-_002aLOAD_002dTRUENAME_002a-have-weird-values_002c-help_0021"></span><h4 class="subsection">13.6.9 *LOAD-PATHNAME* and *LOAD-TRUENAME* have weird values, help!</h4>
<span id="index-_002aLOAD_002dPATHNAME_002a"></span>
<span id="index-_002aLOAD_002dTRUENAME_002a"></span>
<p>Conventional Common Lisp code may use <code>*LOAD-TRUENAME*</code> or <code>*LOAD-PATHNAME*</code> to find
files adjacent to source files. This will generally <em>not</em> work in
ASDF-loaded systems. Recall that ASDF relocates the FASL files it
builds, typically to a special cache directory. Thus the value of
<code>*LOAD-PATHNAME*</code> and <code>*LOAD-TRUENAME*</code> at load time, when ASDF is loading your system,
will typically be a pathname in that cache directory, and useless to you
for finding other system components.
</p>
<p>There are two ways to work around this problem:
</p><ol>
<li> <span id="index-system_002drelative_002dpathname-1"></span>
Use the <code>system-relative-pathname</code> function. This can readily be
used from outside the system, but it is probably not good software
engineering to require a source file <em>of</em> a system to know what
system it is going to be part of. Contained objects should not have to
know their containers.
</li><li> Store the pathname at compile time, so that you get the pathname of the
source file, which is presumably what you want. To do this, you can
capture the value of <code>(or *compile-file-pathname* *load-truename*)</code>
(or <code>*LOAD-PATHNAME*</code>, if you prefer)
in a macro expansion or other compile-time evaluated context.
</li></ol>
</div>
</body>
</html>