Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Eric Timmons
asdf
Commits
2a263463
Commit
2a263463
authored
Jan 28, 2016
by
Francois-Rene Rideau
Browse files
Minor edits and reformating
parent
4d97d896
Changes
2
Hide whitespace changes
Inline
Side-by-side
README.md
View file @
2a263463
...
...
@@ -13,8 +13,9 @@ If you come from the C/C++ world, ASDF covers a bit of what each of
it orchestrates the compilation and dependency management,
handles some of the portability issues, dynamically finds and loads code,
and offers some portable system access library.
Except everything is different in Common Lisp, and ultimately much simpler,
though it does require acquiring some basic concepts.
Except everything is different in Common Lisp, and ultimately much simpler overall,
though it does require acquiring some basic concepts
that do not exactly match those of the C and Unix world.
Importantly, ASDF builds all software in the current Lisp image,
as opposed to building software into separate processes.
...
...
@@ -130,7 +131,7 @@ of its dependencies, you can do it with:
ASDF by default uses Clozure Common Lisp (CCL) to run the scripts that orchestrate its tests.
By defining and exporting the variable LISP to be one of
`ccl`
,
`sbcl`
or
`allegro`
, you
By defining and exporting the variable
`
LISP
`
to be one of
`ccl`
,
`sbcl`
or
`allegro`
, you
can have it use an alternate Common Lisp implementation instead.
Install CCL (respectively SBCL or Allegro) and make sure an executable called
`ccl`
(respectively
`sbcl`
or
`alisp`
) is in your
`PATH`
,
...
...
@@ -192,7 +193,7 @@ you can either do something similar, or expand the source for `cl-launch` with
What has changed?
-----------------
You can consult the
[
d
ebian/c
hangelog
](
d
ebian/c
hangelog
)
for an overview of the
You can consult the
[
d
oc/C
hangelog
](
d
oc/C
hangelog
)
for an overview of the
significant changes in each release, and
the
`git log`
for a detailed description of each commit.
...
...
uiop/lisp-build.lisp
View file @
2a263463
...
...
@@ -641,25 +641,26 @@ possibly in a different process. Otherwise just call THUNK."
"This function provides a portable wrapper around COMPILE-FILE.
It ensures that the OUTPUT-FILE value is only returned and
the file only actually created if the compilation was successful,
even though your implementation may not do that
, and including
an optional call to an
user-provided consistency
check
function COMPILE-CHECK;
even though your implementation may not do that
. It also checks an optional
user-provided consistency function COMPILE-CHECK
to determine success
;
it will call this function if not NIL at the end of the compilation
with the arguments sent to COMPILE-FILE*, except with :OUTPUT-FILE TMP-FILE
where TMP-FILE is the name of a temporary output-file.
It also checks two flags (with legacy british spelling from ASDF1),
*COMPILE-FILE-FAILURE-BEHAVIOUR* and *COMPILE-FILE-WARNINGS-BEHAVIOUR*
with appropriate implementation-dependent defaults,
and if a failure (respectively warnings) are reported by COMPILE-FILE
with
consider
i
t an error unless the respective behaviour flag
and if a failure (respectively warnings) are reported by COMPILE-FILE
,
it will
consider
tha
t an error unless the respective behaviour flag
is one of :SUCCESS :WARN :IGNORE.
If WARNINGS-FILE is defined, deferred warnings are saved to that file.
On ECL or MKCL, it creates both the linkable object and loadable fasl files.
On implementations that erroneously do not recognize standard keyword arguments,
it will filter them appropriately."
#+
(
or
clasp
ecl
)
(
when
(
and
object-file
(
equal
(
compile-file-type
)
(
pathname
object-file
)))
(
format
t
"Whoa, some funky ASDF upgrade switched ~S calling convention for ~S and ~S~%"
'compile-file*
output-file
object-file
)
(
rotatef
output-file
object-file
))
#+
(
or
clasp
ecl
)
(
when
(
and
object-file
(
equal
(
compile-file-type
)
(
pathname
object-file
)))
(
format
t
"Whoa, some funky ASDF upgrade switched ~S calling convention for ~S and ~S~%"
'compile-file*
output-file
object-file
)
(
rotatef
output-file
object-file
))
(
let*
((
keywords
(
remove-plist-keys
`
(
:output-file
:compile-check
:warnings-file
#+
clisp
:lib-file
#+
(
or
clasp
ecl
mkcl
)
:object-file
)
keys
))
...
...
@@ -670,7 +671,7 @@ it will filter them appropriately."
(
object-file
(
unless
(
use-ecl-byte-compiler-p
)
(
or
object-file
#+
ecl
(
compile-file-pathname
output-file
:type
:object
)
#+
ecl
(
compile-file-pathname
output-file
:type
:object
)
#+
clasp
(
compile-file-pathname
output-file
:output-type
:object
))))
#+
mkcl
(
object-file
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment