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
asdf
asdf
Commits
c5bee9d9
Commit
c5bee9d9
authored
Dec 10, 2012
by
Francois-Rene Rideau
Browse files
2.26.19: Fix a format string.
Also fix some texinfo syntax.
parent
f2a2d29e
Changes
3
Hide whitespace changes
Inline
Side-by-side
asdf.asd
View file @
c5bee9d9
...
...
@@ -14,7 +14,7 @@
:licence
"MIT"
:description
"Another System Definition Facility"
:long-description
"ASDF builds Common Lisp software organized into defined systems."
:version
"2.26.1
8
"
;; to be automatically updated by bin/bump-revision
:version
"2.26.1
9
"
;; to be automatically updated by bin/bump-revision
:depends-on
()
:components
((
:file
"asdf"
)))
...
...
asdf.lisp
View file @
c5bee9d9
;;; -*- mode: Common-Lisp; Base: 10 ; Syntax: ANSI-Common-Lisp ; coding: utf-8 -*-
;;; This is ASDF 2.26.1
8
: Another System Definition Facility.
;;; This is ASDF 2.26.1
9
: Another System Definition Facility.
;;;
;;; Feedback, bug reports, and patches are all welcome:
;;; please mail to <asdf-devel@common-lisp.net>.
...
...
@@ -118,7 +118,7 @@
;; "2.345.6" would be a development version in the official upstream
;; "2.345.0.7" would be your seventh local modification of official release 2.345
;; "2.345.6.7" would be your seventh local modification of development version 2.345.6
(
asdf-version
"2.26.1
8
"
)
(
asdf-version
"2.26.1
9
"
)
(
existing-asdf
(
find-class
'component
nil
))
(
existing-version
*asdf-version*
)
(
already-there
(
equal
asdf-version
existing-version
)))
...
...
@@ -2329,11 +2329,11 @@ PREVIOUS-TIME when not null is the time at which the PREVIOUS system was loaded.
;; Warn if some files are missing:
;; either our model is wrong or some other process is messing with our files.
(
when
(
and
just-done
(
not
all-present
))
(
warn
"~A completed without
~*~@[
its input file~:p~{ ~S~}~]~
~
@[
or~]
~*~@[
its output file~:p~*~{ ~S~}~]"
(
warn
"~A completed without
~:[~*~;~*
its input file~:p~
2:*~
{ ~S~}~
*~
]~
~
:[~;
or~]
~:[~*~;~*
its output file~:p~
2:
*~{ ~S~}~
*~
]"
(
operation-description
o
c
)
(
length
missing-in
)
missing-in
(
and
missing-in
missing-out
)
(
length
missing-out
)
missing-out
))
missing-in
(
length
missing-in
)
(
and
missing-in
missing-out
)
missing-out
(
length
missing-out
)))
;; Note that we use stamp<= instead of stamp< to play nice with generated files.
;; Any race condition is intrinsic to the limited timestamp resolution.
(
if
(
or
just-done
;; The done-stamp is valid: if we're just done, or
...
...
doc/asdf.texinfo
View file @
c5bee9d9
...
...
@@ -1460,7 +1460,7 @@ both of them apply to systems that are dependencies and were already compiled.
To see what @code
{
operate
}
would do, you can use:
@example
(asdf::traverse (make-instance
@var
{
operation-class
}
{
@var
{
initargs
}
...
}
) (find-system
@var
{
system-name
}
))
(asdf::traverse (make-instance operation-class
initargs ...) (find-system system-name))
@end example
@end deffn
...
...
@@ -1578,8 +1578,8 @@ On your build platform, you run something like that:
And on your delivery platform, a form like this is evaluated
in a prologue or at some point before you save your image:
@example
@code
{
(defsystem
@var
{
:mysystem
}
:class :precompiled-system
:fasl
@var
{
(some expression that will evaluate to a pathname)
}
)
}
(defsystem :mysystem :class :precompiled-system
:fasl (some expression that will evaluate to a pathname)
)
@end example
Of course, @emph
{
before
}
you define such systems,
...
...
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