116 lines
5.3 KiB
HTML
116 lines
5.3 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>How can I produce a binary at a specific path from sources at a specific path (ASDF Manual)</title>
|
|
|
|
<meta name="description" content="How can I produce a binary at a specific path from sources at a specific path (ASDF Manual)">
|
|
<meta name="keywords" content="How can I produce a binary at a specific path from sources at a specific path (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="LOAD_002dPATHNAME-has-a-weird-value.html" rel="prev" title="LOAD-PATHNAME has a weird value">
|
|
<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="How-can-I-produce-a-binary-at-a-specific-path-from-sources-at-a-specific-path">
|
|
<div class="header">
|
|
<p>
|
|
Previous: <a href="LOAD_002dPATHNAME-has-a-weird-value.html" accesskey="p" rel="prev">*LOAD-PATHNAME* and *LOAD-TRUENAME* have weird values, help!</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> [<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="How-can-I-produce-a-binary-at-a-specific-path-from-sources-at-a-specific-path_003f"></span><h4 class="subsection">13.6.10 How can I produce a binary at a specific path from sources at a specific path?</h4>
|
|
<span id="index-bundle-operations-2"></span>
|
|
<span id="index-program_002dop-2"></span>
|
|
|
|
<p>Especially when integrating with outside build systems, it’s useful to have
|
|
fine-grained control over where ASDF puts output files. The following is an
|
|
example of a build script that takes the directory to find the source and the
|
|
path to put the resulting binary at, and compiles a system there.
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example">(in-package :cl-user)
|
|
|
|
;; Tell ASDF where to find your source files. This may not
|
|
;; be necessary if you've already configured this elsewhere.
|
|
(asdf:initialize-source-registry
|
|
`(:source-registry
|
|
:inherit-configuration
|
|
(:directory ,(uiop:getenv-absolute-directory "SRC"))))
|
|
|
|
;; Set the output pathname when building the system.
|
|
(defmethod asdf:output-files ((o asdf:image-op)
|
|
(system (eql (asdf:find-system <var>foo</var>))))
|
|
(declare (ignorable system))
|
|
(values (list (uiop:getenv-pathname "OUT")) t))
|
|
|
|
;; Build the system.
|
|
(asdf:operate-on-system 'asdf:program-op <var>foo</var>)
|
|
(uiop:quit)
|
|
</pre></div>
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</body>
|
|
</html>
|