Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jan Moringen
asdf
Commits
2414d39e
Commit
2414d39e
authored
10 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
Trivial documentation update
parent
a51aff0f
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/index.html
+30
-26
30 additions, 26 deletions
doc/index.html
uiop/README.md
+20
-10
20 additions, 10 deletions
uiop/README.md
with
50 additions
and
36 deletions
doc/index.html
+
30
−
26
View file @
2414d39e
...
...
@@ -84,7 +84,9 @@
call other programs and parse their output,
compile Lisp code, muffle conditions, or configure Lisp software.
See its
<a
href=
"https://gitlab.common-lisp.net/asdf/asdf/tree/master/uiop/README.md"
>
README.md
</a>
.
<a
href=
"https://gitlab.common-lisp.net/asdf/asdf/tree/master/uiop/README.md"
>
README.md
</a>
for an overview,
and the documentation as extracted from its docstrings by
<a
href=
"http://bimib.disco.unimib.it/people/Marco.Antoniotti/Projects/CL/HELAMBDAP/tests/asdf-uiop/docs/html/dictionary/dictionary.html"
>
HEΛP
</a>
.
</p>
<p><tt>
uiop
</tt>
is distributed as part of the
<tt>
ASDF
</tt>
,
its source code is transcluded in the single-file
<tt>
asdf.lisp
</tt>
being distributed
...
...
@@ -120,14 +122,15 @@
<a
href=
"https://bugs.launchpad.net/asdf/+bug/1230368"
><tt>
quick-build
</tt></a>
(also reimplemented as the ASDF extension
<a
href=
"https://gitlab.common-lisp.net/asdf/asdf-package-system"
><tt>
asdf-package-system
</tt></a>
; similar to
<tt>
faslpath
</tt>
below).
><tt>
asdf-package-system
</tt></a>
, now part of ASDF 3;
similar to
<tt>
faslpath
</tt>
below).
</li>
<li>
Fran
ç
ois-Ren
é
Rideau's
<a
href=
"https://common-lisp.net/project/xcvb/"
><tt>
XCVB
</tt></a>
(building object and image files deterministically and in parallel,
but not actively maintained since 2012;
thanks to its new build model,
ASDF
3
could conceivably be
modified
t
o support these features
).
a hypothetical
ASDF
4
could conceivably be
evolved to support these features
t
hanks to the groundwork laid by ASDF 3
).
</li>
<li>
Drew McDermott's
<a
href=
"http://cs-www.cs.yale.edu/homes/dvm/"
><tt>
YTools
</tt></a>
...
...
@@ -187,16 +190,16 @@
<td
align=
"left"
><tt>
mcl xcl
</tt></td></tr>
<tr><th
align=
"left"
>
Proprietary
</th>
<td
align=
"left"
><tt>
allegro
</tt></td>
<td
align=
"left"
><tt>
lispworks
mocl
</tt></td>
<td
align=
"left"
><tt>
cormanlisp genera scl
</tt></td></tr>
<td
align=
"left"
><tt>
lispworks
</tt></td>
<td
align=
"left"
><tt>
cormanlisp genera
mocl
scl
</tt></td></tr>
</table>
<p>
To deal with an implementation that doesn't yet provide ASDF 3,
we provide
<a
href=
"https://common-lisp.net/asdf/asdf/tree/master/tools/install-asdf.lisp"
>
a script
</a>
that can install ASDF 3
where your implementation goes looking for it
we provide
<a
href=
"https://common-lisp.net/asdf/asdf/tree/master/tools/install-asdf.lisp"
>
a script
</a>
that can install ASDF 3
where your implementation goes looking for it
when you
<tt>
(require "asdf")
</tt>
.
</p><p>
Alternatively, if the implementation provides ASDF 2
Alternatively,
though we don't recommend it,
if the implementation provides ASDF 2
(as do
<tt>
lispworks mocl xcl
</tt>
or older versions of some implementations)
or an overly old version of ASDF 3,
you can download, install and configure a more recent ASDF 3,
...
...
@@ -329,7 +332,7 @@ XCL (Peter Graves) <gnooth@gmail.com>
to compute the actual dependencies in a big ASDF system.
</li>
<li><a
href=
"https://common-lisp.net/project/qitab/"
><tt>
poiu
</tt></a>
,
to compile a system in parallel.
</li>
to compile a system in parallel
on a multiprocessor machine
.
</li>
<li><a
href=
"https://common-lisp.net/project/asdf-system-connections/"
><tt>
asdf-system-connections
</tt></a>
,
lets you specify systems that are automatically loaded when
...
...
@@ -337,19 +340,10 @@ XCL (Peter Graves) <gnooth@gmail.com>
<li><a
href=
"http://www.lrde.epita.fr/~didier/software/lisp/misc.php#asdf-flv"
><tt>
asdf-flv
</tt></a>
,
to bind file-local variables around the compilation of some files.
</li>
<li><a
href=
"http://gitlab.common-lisp.net/asdf/asdf-package-system"
><tt>
asdf-package-system
</tt></a>
,
to compile Lisp source files with one package per file
that also determines dependencies, in the style of
<a
href=
"https://bugs.launchpad.net/asdf/+bug/1230368"
><tt>
quick-build
</tt></a>
or
<a
href=
"http://www.cliki.net/faslpath"
><tt>
faslpath
</tt></a>
(this functionality is built into recent versions of ASDF 3.1 and later,
but this package exists for backward compatibility with earlier versions of ASDF 3;
search the manual for
<tt>
package-inferred-system
</tt>
).
</ul>
<p>
Former extensions, now superseded, include:
</p>
<ul>
<li><tt>
asdf-binary-locations
</tt>
allow
ed
one to redirect where ASDF create
s
its output files,
<li><tt>
asdf-binary-locations
</tt>
used to
allow one to redirect where ASDF
1
create
d
its output files,
so they don't clash between implementations and don't pollute source directories.
It is superseded by
<tt>
asdf/defsystem
</tt>
's builtin
<tt>
asdf-output-translations
</tt>
mechanism;
...
...
@@ -366,16 +360,26 @@ XCL (Peter Graves) <gnooth@gmail.com>
a standalone executable program (on supported implementations),
or an image containing your system precompiled.
</li>
<li><tt>
asdf-condition-control
</tt>
, initially part of XCVB's
<tt>
xcvb-driver
</tt>
,
allowed you to muffle uninteresting conditions during compilation.
Is now superseded by equivalent functionality in
<tt>
uiop
</tt>
.
</li>
<li><a
href=
"http://gitlab.common-lisp.net/asdf/asdf-package-system"
><tt>
asdf-package-system
</tt></a>
,
to compile Lisp source files with one package per file
that also determines dependencies, in the style of
<a
href=
"https://bugs.launchpad.net/asdf/+bug/1230368"
><tt>
quick-build
</tt></a>
or
<a
href=
"http://www.cliki.net/faslpath"
><tt>
faslpath
</tt></a>
(this functionality is built into recent versions of ASDF 3.1 and later,
but this package exists for backward compatibility with earlier versions of ASDF 3;
search the manual for
<tt>
package-inferred-system
</tt>
).
</li>
<li><tt>
asdf-utils
</tt>
was a collection of utilities that originated with ASDF.
It is now superseded by
<tt>
uiop
</tt>
, aka
<tt>
asdf/driver
</tt>
,
which is part of ASDF,
and exports its functionality
in its own package
<tt>
uiop
</tt>
.
</li>
<li><tt>
asdf-condition-control
</tt>
, initially part of XCVB's
<tt>
xcvb-driver
</tt>
,
allowed you to muffle uninteresting conditions during compilation.
Is now superseded by equivalent functionality in
<tt>
uiop
</tt>
.
</li>
</ul>
<h3>
Contributing
</h3>
...
...
@@ -497,9 +501,9 @@ XCL (Peter Graves) <gnooth@gmail.com>
<a
class=
"nav"
href=
"http://www.catb.org/hacker-emblem/"
title=
"hacker"
>
<img
src=
"http://common-lisp.net/project/cl-containers/shared/buttons/hacker.png"
width=
"80"
height=
"15"
title=
"hacker emblem"
alt=
"hacker button"
/></a>
<a
class=
"nav"
href=
"http://www.lisp.org/"
title=
"Association of Lisp Users"
>
<img
src=
"http://common-lisp.net/project/cl-containers/shared/buttons/lambda-lisp.png"
width=
"80"
height=
"15"
title=
"ALU emblem"
alt=
"ALU button"
/></a>
<a
class=
"nav"
href=
"http://common-lisp.net/"
title=
"Common-Lisp.net"
>
<img
src=
"http://common-lisp.net/project/cl-containers/shared/buttons/lisp-lizard.png"
width=
"80"
height=
"15"
title=
"Common-Lisp.net"
alt=
"Common-Lisp.net button"
/></a>
<p><span
class=
"copyright"
Copyright
&
copy
;
2001
-201
4
Daniel
Barlow
and
contributors
</
span
></p>
<p><span
class=
"copyright"
Copyright
&
copy
;
2001
-201
5
Daniel
Barlow
and
contributors
</
span
></p>
<p>
ASDF has an
<a
href=
"http://www.opensource.org/licenses/mit-license.php"
>
MIT style
</a>
license
</p>
<div
id=
"timestamp"
>
Last updated 2015-0
3-28
</div>
<div
id=
"timestamp"
>
Last updated 2015-0
5-05
</div>
</div>
</body>
</html>
This diff is collapsed.
Click to expand it.
uiop/README.md
+
20
−
10
View file @
2414d39e
UIOP the Utilities for Implementation- and OS- Portability
==========================================================
UIOP
,
the Utilities for Implementation- and OS- Portability
==========================================================
=
UIOP is the portability layer of ASDF.
It provides utilities that abstract over discrepancies between implementations,
...
...
@@ -9,9 +9,11 @@ what programmers actually need, to write portable Common Lisp programs.
It is organized by topic in many files, each of which defines its own package
according to its topic: e.g
`pathname.lisp`
will define package
`UIOP/PATHNAME`
and contain utilities related to the handling of pathname objects.
All exported symbols are reexported in a convenience package
`UIOP`
.
All exported symbols are reexported in a convenience package
`UIOP`
,
except for those from
`UIOP/COMMON-LISP`
.
We recommend package
`UIOP`
be used to access all the symbols.
The files that constitute UIOP are, in loading order:
The files that constitute UIOP are, in
dependency
loading order:
*
`package`
: deals with packages and their symbols, most notably including
`define-package`
, a variant of
`defpackage`
capable of hot-upgrade, or
...
...
@@ -21,7 +23,7 @@ The files that constitute UIOP are, in loading order:
*
`common-lisp`
: lets you paper over various sub-standard implementations.
Big offenders are Corman, GCL, Genera, MCL, all of them unmaintained.
Supported without serious issues are:
ABCL, Allegro, CCL, CMUCL, CLISP, ECL, LispWorks, MKCL, SBCL, SCL, XCL.
ABCL, Allegro, CCL, CMUCL,
CLASP,
CLISP, ECL, LispWorks, MKCL, SBCL, SCL, XCL.
*
`utility`
: provides macros and functions that do not involve I/O; it handles
control-flow, (p)lists, characters, strings, functions, classes, conditions,
...
...
@@ -63,8 +65,8 @@ The files that constitute UIOP are, in loading order:
runs hooks around compilation (to e.g. control optimizations or syntax),
identifies the pathname of the current file, combines FASLs, etc.
*
`configuration`
: helps you
define
portable configuration files,
using best
practices to define and validate syntax, search standard paths,
*
`configuration`
: helps you portabl
y locate and pars
e configuration files,
using best
practices to define and validate syntax, search standard paths,
let users specify pathnames or pathname patterns, etc.
*
`backward-driver`
: provides backward-compatibility with earlier incarnations
...
...
@@ -95,6 +97,10 @@ it only extracts information from the first package:
http://quickdocs.org/uiop/api
See bug report:
https://github.com/fukamachi/quickdocs/issues/24
Using UIOP
----------
...
...
@@ -123,11 +129,15 @@ evolved from ASDF 2's internal utilities and portability layer.
It has since fully superseded functionality from the following libraries:
ASDF-UTILS (UIOP carries on the ASDF 2 utilities that this exported),
CL-FAD (UIOP's pathname and filesystem functions are much more portable),
CL-LAUNCH (UIOP took its image and command-line argument handling from it),
EXTERNAL-PROGRAM, TRIVIAL-SHELL and XCVB-DRIVER (UIOP's run-program is better),
SLIME's swank-loader (UIOP has better compilation and API identification),
CL-LAUNCH (UIOP took its image and command-line argument handling),
EXTERNAL-PROGRAM, TRIVIAL-SHELL and XCVB-DRIVER (UIOP's run-program evolved
from XCVB-DRIVER's, and so did its condition muffling),
SLIME's swank-loader (UIOP has better compilation and ABI identification),
TRIVIAL-BACKTRACE (UIOP/IMAGE has all of it and more), etc.
UIOP also captures a large subset of the functionality from TRIVIAL-FEATURES,
and a small subset of the functionality from ALEXANDRIA or FARE-UTILS.
We recommend you use UIOP instead of any of the above, where applicable,
since UIOP is more portable, more robust, more ubiquitous, better designed,
better documented, etc.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment